BluPrint
Product
Documentation
Login
Documentation
Get Started
Use Cases & Guides
Tutorials
Projects
Projects overviewInside a projectCreating a projectStatus & lifecycleMembers & rolesSprints & milestonesProject SnapshotProject settings
Tasks
Customers & CRM
Business Brain
Views
The Associate (AI)
AI Helpers
Communication
Documents & Knowledge
Time Tracking
Companies & Workspaces
Roles & Permissions
Billing
Account & Profile
Security & Compliance
Integrations
FAQ
Release LogSoon
ResourcesSoon
DocumentationProjectsProjects overview

Projects overview

A project is BluPrint's delivery workspace for a defined body of work. It brings together planning, execution, knowledge, communication, meetings, and customer context.

Where a project lives

  • A Company is the tenant and top-level security boundary.
  • A Workspace groups related projects.
  • A Project belongs to a company/workspace and has its own authorised members, lead, schedule, documents, and activity.

The selected company/workspace in the V2 sidebar controls where new projects are created and which projects appear.

Project surfaces

Depending on your role and project configuration, a project includes:

  • Overview/Snapshot — current health, key signals, and recommended attention.
  • Tasks/Board — tasks, statuses, priorities, assignees, subtasks, and dependencies.
  • Gantt/Timeline — schedule, dependencies, milestones, and critical-path context.
  • Documents — project folders, files, versions, metadata, and knowledge retrieval.
  • Comms — project conversation and activity.
  • Meetings — meeting records, preparation/waiting flows, notes, and related actions.
  • Activity/Audit — authorised operational history.
  • Settings/Automations — project configuration available to eligible roles.

Customer links

An account or deal can link to a delivery project. Authorised CRM and project users can use that seam to understand how delivery health affects the relationship. The link never grants access to a project or sealed account by itself.

Members and access

Company membership is required, then project membership/role and object permissions narrow what each person can see or change. Owners/admins/managers may have company-wide authority according to the permission; members and viewers remain project/object scoped.

Work with the Associate

On a project route, the Associate can attach the active project as context. It can explain authorised project state, retrieve relevant project/company knowledge, and propose supported staged actions. Remove the project chip when you want a broader company-level conversation.

Link delivery to the relationship

When a project delivers for a customer, link it from the account/deal so authorised teams can see customer and delivery context together.

Next

  • Creating a project
  • Inside a project
  • Members & roles
  • Customers & CRM
  • The Associate

Last updated: 2026-08-05

Next Inside a project

On this page

  • Where a project lives
  • Project surfaces
  • Customer links
  • Members and access
  • Work with the Associate
  • Next