What you need to know
A project's page shows one piece of work: its values at the top, then every , grouped by the stage it is at, with the people on it and what it waits on. Anyone who may see the project reads all of it. A department manager also changes the values, puts people on tasks, and brings back tasks that were set aside.
In a project whose template has tasks that can repeat, each one filed is a . Anyone in the department who can change work files one with New ticket and takes one with Take it. See Tickets.
How to get here
- From Workflow Projects: select Open on the project's row.
- From My Tasks: select the title of a card. The page opens with that task marked in purple, and a Back to My Tasks button.
- From a group: select a member. The page then has Back to the group.
- From an engagement's Overview: under Progress, select Open WorkFlow Project on a property's row. The page then has Back to the engagement. Open Property beside it opens the property.
- From the Workflow page of a property or an engagement: select the kind of work under a task. The page opens with that task marked.
At the top right, People opens Who has access. Back to the list returns to Workflow Projects.
The purple bar at the top of the page ends with the project's name, here and on Who has access. Select Workflow Projects in it to go back to the list.
A project started on a property or an engagement is named by that record first, then by its kind of work, such as Example Holdings · Engagement intake, so two engagements' projects of the same kind read apart. A name someone typed shows as typed, with the record in front when the name does not already say it. The round link beside the name opens the property or engagement.
Fields: the project's values
Fields holds the project's values, such as a yes or no answer, an amount or a date. Each value is a that its template defines. A manager types or picks any value in place. The person on a task that asks a question changes that one value too, and sees the rest read only. Everyone else sees the same values, read only.
- A value saves when you leave the box, press Enter, or pick from a list. Press Escape to put the old value back.
- To empty a value, clear the box. A list has a small × to clear it.
- Some tasks depend on a value. When a value changes, a task can become live or Not applicable, and a message names each task that changed. Read Why a task is “Not applicable”.
Tasks by stage
Tasks by stage lists every task, grouped by the stage it is at, in the template's order. The line under the title counts the tasks and how many active ones have nobody on them.
On a narrow window each task stacks into two columns, task and state, with the rest below the title.
Tickets, for some templates
In a project whose template has tasks that can repeat, such as Tech / Development's ticket project, each of those tasks is a kind of ticket: for example Problem report, Bug, Idea and IT help. The project starts with none of them. Each one is filed, worked and finished on its own.
- New ticket, above Tasks by stage, files one: its kind, a title, and the fields the template asks each ticket to fill in. See File a ticket.
- A new ticket starts in the first stage with Nobody yet. Take it on its row puts you on it, and nobody else. See Take a ticket.
- A ticket's title opens the ticket: its kind and its own fields, such as its Description, Link and Priority. These are not in the project's Fields: each ticket has its own.
- A ticket emails only the people it concerns, and only people who can read it. See Who is told.
Route, for some templates
Some templates group their tasks into stations along a route. For those projects the page also has a Route section above Fields, with a Map view and a Details view. Select a station on the map to see its tasks. Projects whose template has no stations do not show this section.
The heading names whose tasks the map counts, such as Route: Engagement intake tasks only. The line under it says how many tasks this project has and where the other work's tasks are: on an engagement's project, the property's work is on the property's own route. See Reading the route map.
Files and comments
Under the tasks, Files holds the project's own documents and Comments its conversation: each comment with its replies under it. They belong to the project as a whole; each task has its own on its card in the Work panel. The count beside each heading is how many there are.
Everyone who can open the project reads them, opens a file with Open and saves it with Save As. See Add files and comments to your work.
What you can do here
- Add files and comments to your work, under Files and Comments
- Assign or reassign a task
- Change a project's values
- File a ticket, in a project that takes tickets
- Take a ticket that nobody has taken yet
- Skip a task, and bring it back
- Give someone access to the project, from People
- Move the work to a newer version, with Move to v5 (the newer version's number) at the top. It shows when a newer version is published. When that version cannot take this work, it is grayed out, and pointing at it says why.
Who can do what here
A department manager or a company administrator sees Assign, the × beside each person, Bring back, Move to v5 when a newer version is published, and values they can change. The person on a task that asks a question can change that value, and nothing else. Everyone else sees the same page with no buttons: the values are read only, and nothing is grayed out because there is nothing to press.
In a project that takes tickets, a contributor, a department manager and a company administrator also see New ticket and Take it, and change a ticket's own fields. A manager sees Take it above Assign. An executive observer opens a ticket from its title and reads it, with no buttons.
Under Files and Comments, a contributor, a department manager and a company administrator add files, comment and reply; each removes the files they added and edits or deletes their own comments. An executive observer reads them, with no place to add and no buttons but Open and Save As.
Good to know
On a canceled project nobody can change values, tasks, files or comments. A message says so: “This work is canceled. Reactivate it from the list before changing its fields or its tasks.” The same is true while the project's property or engagement is deleted. See When its property or engagement is deleted.When its property or engagement is deleted
When the property or the engagement that the work is for is deleted, the project leaves every list: Workflow Projects, My Tasks, its groups, and the email about its work. A department manager still finds it on Workflow Projects under Paused. Its page still opens, from that row or from a link, and says so under its name:
“This property was deleted on 10/06/2026; its work is paused until it is restored.”
- Nobody can change the work while the record is deleted: Assign, Bring back and the values are not offered, and a message headed Work paused gives the same sentence.
- People still works: you can still see and change who has access.
- Nothing in the work is changed. When an administrator restores the record, the project is back on every list, exactly as it was. See A project or its tasks disappeared.
Things to know
- A removed task does not show on this page, and cannot be brought back from here.
- Done, skipped and not-applicable tasks keep the people who were on them, with no buttons.