Projects

Projects organize delivery work after a sale or for any internal initiative. A project can connect to an account or deal, then break the work into milestones and jobs with owners, dates, priorities, and progress.

Find and organize projects

Open Projects from the Operations section. The page provides three views:

View	Best for
Gantt	Seeing projects, milestones, and jobs on one timeline and adjusting planned dates
List	Sorting, filtering, editing, and selecting projects in a table
Kanban	Following projects by status or a supported custom select property

Gantt is the default view. List and Kanban use the same filters and saved Table Views, so a team can keep views such as “My Projects” or “Overdue Delivery.”

The standard tabs are All, My, In Progress, Overdue, and On Hold. Filters include project, owner, status, priority, job status, due status, expected end date, and create date.

From List view, users with the required permissions can select projects and bulk edit, assign, delete, or create follow-up tasks.

Create a project

A project includes:

name and description
status and priority
owner
optional account and deal
expected and actual start and end dates
tags
optional pipeline and stage
native and custom properties

Project statuses are Not Started, In Progress, On Hold, Completed, and Cancelled. Priorities are Low, Medium, High, and Critical.

Use status for the project’s general state. Use a Project pipeline when the organization needs a separate, configurable delivery process with ordered stages and transition rules. See Pipelines and Stages.

Create from a template

Choose a template while creating a project to generate its milestone and job structure. If the template uses project roles, map each role to the appropriate team member before creating the project.

Templates can define:

milestones and their order
jobs inside each milestone
start offsets and durations relative to the project start date
role responsibilities
milestone completion, unlocking, and approval behavior

Configure reusable structures in Settings → Project Templates.

Work from the project record

Opening a project shows the project record without losing the list context. The full record includes these tabs:

Overview for project information, linked account or deal, owner, tags, and the AI summary when available
Milestones for delivery phases and their jobs
Comments for internal collaboration
Files for project attachments
Timeline for record activity and changes

Keep the expected dates current. Gantt and overdue filters depend on them, while actual dates show what happened during delivery.

Milestones

Milestones represent phases or deliverables. Their status can move through:

Locked → Unlocked → In Progress → Pending Approval → Completed

A milestone can carry expected and actual dates, progress, and these controls:

Setting	Effect
Auto unlock	Unlocks the next milestone after completion
Completion rule	Uses strict completion or weighted job progress
Allow early start	Permits jobs to start before the milestone unlocks
Require all jobs	Prevents completion until every required job is complete
Require approval	Sends the milestone through its configured approval role
Lock on achieve	Locks the milestone after it is completed

Choose strict completion when every job must finish. Use weighted completion when some jobs contribute more to progress than others.

Jobs

Jobs are the actionable work inside a milestone. A job can have:

Pending, In Progress, Completed, Blocked, or Cancelled status
priority
an assigned project role and specific user
start and due dates
estimated and actual hours
a weight used by weighted milestone completion

Completing a job recalculates milestone and project progress. Depending on the milestone settings, completion can also finish the milestone and unlock the next one.

Project roles

Project roles describe responsibilities such as Project Manager, Designer, Developer, or QA. They are reusable across templates and projects.

In Settings → Project Roles, administrators can create roles and assign preferred users. A project can then map those roles to its actual team members. Jobs assigned to a role follow the project-specific mapping.

Properties and pipelines

Projects support native, custom, and computed Properties. Administrators can add fields, group them, apply validation or conditional requirements, and use supported select properties to organize Kanban boards.

Projects also support Pipelines and Stages. Project record layouts are not currently configurable in Settings → Objects; use Properties for additional project data.

Visibility and permissions

Project visibility follows workspace data-visibility rules. A user may also see a project when they are assigned to one of its jobs. Create, update, and delete actions still require the matching project permission.