BluprintDocumentation
Open Bluprint
Get Started
Use Cases & Guides
Tutorials
Projects
Tasks
Views
The Associate (AI)
AI Helpers
Communication
Documents & Knowledge
Time Tracking
Companies & Workspaces
OverviewCompaniesWorkspacesMembers & accessInvitations & join requests
Roles & Permissions
Billing
Account & Profile
Security & Compliance
IntegrationsSoon
FAQ
Release LogSoon
ResourcesSoon
DocumentationCompanies & WorkspacesCompanies & Workspaces

Companies & Workspaces

Everything in Bluprint sits inside a clear structure. Understanding it makes the rest of the product — permissions, the Associate, projects — click into place.

The hierarchy

LevelWhat it is
CompanyYour organisation — the top level, and the boundary your data lives inside.
WorkspaceA space within the company that groups related projects (e.g. a team, client, or department).
ProjectA body of work inside a workspace.
TaskThe individual units of work inside a project.

So the shape is: Company → Workspaces → Projects → Tasks.

Why it's built this way

  • A company keeps your data separate. Each company's data lives in its own isolated store, so one organisation's work is never mixed with another's.
  • Workspaces keep work organised. Instead of one giant pile of projects, you group them by purpose — one source of truth per team or client — and control who sees what.
  • Access flows down the levels. Being in a company doesn't automatically mean seeing every workspace; membership is layered, which keeps things both tidy and secure.

Where this connects

Roles decide what people can do at each level — covered in Roles & Permissions. The Associate also respects this structure: it only ever sees the workspaces you can.

Start here

  • Companies — your tenant, owner, and company-wide settings.
  • Workspaces — how to group projects and tailor settings.
  • Members & access — the two levels of membership.
  • Invitations & join requests — getting people in.

Next

  • Companies
  • Workspaces

Last updated: 2026-05-31

Next Companies

On this page

  • The hierarchy
  • Why it's built this way
  • Start here
  • Next