This guide covers creating an Operations project, structuring it into phases and milestones, and putting a team on it.
Before you start
- You need the operations projects-manage permission to create or edit projects (view-only users can browse).
- A project only needs a name to be created — everything else is optional.
- To name a project manager or add team members, those people must be members of your organisation.
Steps
- Go to Operations → Projects and start a new project.
- Complete the project fields:
- Name — required. Up to 200 characters.
- Description — optional. Up to 4000 characters.
- Status — one of Planning, Active, On hold, Completed or Cancelled.
- Start date and Target date — optional.
- Project manager — optional. Chosen from your organisation’s people.
- Client account — optional link to a CRM account, with a Client visible toggle.
- Documents — optional references to documents already held in the platform (up to 50).
[screenshot: the new-project form]
- Add phases to band the work. Each phase takes a Name (required), optional Description, a Sort order, and optional Start and Target dates. Phases are ordered by their sort value.
- Add milestones. Each takes a Name (required), optional Description, Status (Pending, In progress, Missed), a Due date, a Sort order, a Client visible toggle, and may be tied to one of the project’s phases.
[screenshot: milestones listed under a phase]
- Build the team from Roles. Pick a person and give them a role — Manager, Member, Reviewer or Stakeholder.
- When a milestone is delivered, choose Request acceptance and name an approver (who must be someone other than yourself). This opens an approval and moves the milestone to Awaiting acceptance; it becomes Accepted only once that approval is granted.
Result
The project holds its phases, milestones and team, and its health is recomputed as milestones change. Milestone acceptance runs through the platform approval flow rather than by editing status directly.