V2 Dashboard

The V2 dashboard is BluPrint's company/workspace shell. It replaces the retired Personal Dashboard and keeps navigation, current company/workspace, notifications, approvals, calendar, search, and the Associate available while you move between lenses.

Navigation adapts to your selected company membership and enabled capabilities:

Home — company/workspace orientation and current signals.
Comms — company communication available to your role.
My Tasks — work assigned to you.
My Pipeline — deals assigned to you when CRM is available.
Projects — projects in the selected workspace/company.
Portfolio — cross-project coordination for eligible roles.
Customers — company Pipeline and Accounts.
Knowledge — Company Knowledge and Company Brain.
Business — insights as they become available and billing for eligible roles.
Integrations — provider management; GitHub will appear only for the Alesko.ai internal canary after activation, while customer companies and other providers remain disabled.
Settings — personal and company settings permitted by your role.

CRM is a core capability for every active company. The sidebar still respects role-based access and the global emergency safety switch.

Company and workspace context

Use the company/workspace control in the sidebar to change context. BluPrint refreshes membership, role, CRM state, branding, projects, and API scope for the selected company. Persisted browser IDs are accepted only when they belong to the freshly loaded membership list.

Top bar

The top bar provides global search, feedback, and the active workspace/project context. Notifications, Approvals, and Calendar controls stay in the shell so they are reachable from every dashboard lens.

Role-aware views

Your company role chooses the default altitude:

members/guests focus on execution;
managers gain coordination and portfolio surfaces;
owners/admins gain company steering and management surfaces;
viewers remain read-only where supported;
billing-only access does not grant project or CRM visibility.

The sidebar is convenience, not the security boundary. Backend permissions still protect each API and object.

Persistent Associate

The Associate opens from the bottom-centre control. On project routes it can attach the active project; on CRM and knowledge routes it uses only context authorised for your current company and role.

Start with context

Check the selected company and workspace before creating work or asking the Associate to act. This prevents a correct action from landing in the wrong workspace.

Last updated: 2026-08-21

PreviousViews overview Next Kanban board

Left navigation

Navigation adapts to your selected company membership and enabled capabilities:

Home — company/workspace orientation and current signals.

Comms — company communication available to your role.

My Tasks — work assigned to you.

My Pipeline — deals assigned to you when CRM is available.

Projects — projects in the selected workspace/company.

Portfolio — cross-project coordination for eligible roles.

Customers — company Pipeline and Accounts.

Knowledge — Company Knowledge and Company Brain.

Business — insights as they become available and billing for eligible roles.

Integrations — provider management; GitHub will appear only for the Alesko.ai internal canary after activation, while customer companies and other providers remain disabled.

Settings — personal and company settings permitted by your role.

CRM is a core capability for every active company. The sidebar still respects role-based access and the global emergency safety switch.

Role-aware views

Your company role chooses the default altitude:

members/guests focus on execution;

managers gain coordination and portfolio surfaces;

owners/admins gain company steering and management surfaces;

viewers remain read-only where supported;

billing-only access does not grant project or CRM visibility.

The sidebar is convenience, not the security boundary. Backend permissions still protect each API and object.

Persistent Associate

The Associate opens from the bottom-centre control. On project routes it can attach the active project; on CRM and knowledge routes it uses only context authorised for your current company and role.

Start with context

Check the selected company and workspace before creating work or asking the Associate to act. This prevents a correct action from landing in the wrong workspace.