Skip to main content
Projects use several capabilities, not one. Structure, money and rates are deliberately separate, because a project manager may run a project without seeing what it costs.

​
The capabilities that matter

project.manage is the big one. Everything structural goes through it.

​
Which roles hold them

These are the seeded defaults. Custom roles can mix them differently – see /team/custom-roles.
Finance owns money, not delivery. Finance can set a budget and read rates, but cannot create or restructure a project. Project Manager is the mirror image.

​
Capability is not scope

Holding project.manage does not mean you can manage every project. A project manager scoped to their own projects holds project.manage, but only over projects they manage or are staffed on. Both checks run on every action. See /projects/project-visibility.

​
What each capability unlocks on screen

  • You can open projects within your reach and work their tasks.
  • There is no Actions menu – no Archive, Delete or Restore.
  • The Settings tab’s controls are unavailable to you.
  • Section three-dot menus and Add section do not work.

​
Server-side enforcement

Every capability is re-checked when the change is written, not just when the button is drawn. Hiding a control is a convenience; the refusal is what actually protects the data. That means:
  • A saved link into a project you cannot reach behaves like a project that does not exist.
  • A role change takes effect on your next action – no sign-out needed.
  • A control you never see is also a control the server would refuse.

​
Cost visibility is not a plan question

Who may see cost is a capability. What your plan gates is one write: setting a cost rate requires Pro. See /concepts/plans-and-features.

​
App gating

Projects live inside the Projects & tasks app. Several project surfaces depend on other apps too: See /concepts/apps-and-modules.

​
Example

At Northwind Studio, on Website Redesign:

​
Common questions

Not by default. Add project.manage to a custom role if you want them to.
Only with rate.viewCost or time.viewCost. The budget card and the cost column are separate gates on purpose.
Because Finance owns the money surface, not delivery. If your finance lead also runs projects, build a custom role.
Capabilities are set on the role, not per project. What is per project is reach – who is on the roster. Combine a narrow scope with project membership to get the same effect.
Some capabilities can be denied per person. See /team/per-person-permissions.
Being the manager grants reach to that project. It does not grant capabilities – those come from the role.

​
Troubleshooting

Roles and capabilities

All seven roles, all 66 capabilities.

Project visibility

The scope half of access.

Custom roles

Build a role that fits.

Per-person permissions

Deny a capability for one person.

Apps and modules

What switching an app off does.

Client permissions

The same model, for clients.