Who can use Projects
Staff roles decide who can create a project, edit tasks, show it to a client, and open Settings. Client roles are separate.
Applies to Owner Admin Technician
Projects uses your staff role for the PSA area, and a separate role for a client's own Projects app. Organization access still has to include Projects. See Roles and permissions for the organization roles.
Staff in PSA#
| What you can do | Who |
|---|---|
| Open projects, the board, and the timeline | Anyone who can open PSA and whose organization includes Projects |
| Edit tasks, log time, and edit a project | A member or a higher role. A viewer cannot |
| Turn on Show in client portal | A manager, an admin, or an owner |
| Choose New Project on the list | An admin or an owner. Others see Admin or owner role required |
| Open Settings | A Projects admin, or an organization admin or owner |
A viewer who opens Settings sees Settings are restricted and Back to Projects.
A client in the portal#
| What they can do | Who |
|---|---|
| Follow a project you show them | A client of that company, after Show in client portal is on |
| Comment or approve | Only when their portal access includes that action |
| Use their company's own projects | Their account includes Projects, and a company admin has not turned the app off |
| Create and edit those projects | Can edit or Admin |
| Look only | View only |
| Archive, manage request forms, and open Automations | Admin |
If it goes wrong#
- The client says Projects is not available to you. Their provider turned it off, a company admin turned it off, or the account has no seat that includes Projects. The page states which one.
- A technician cannot create a project. That button is for an admin or an owner. They can still work tasks when their role can edit.
What's next#
Was this article helpful?