Project role permissions
The complete breakdown of the three project roles. Manager has full access to everything, so the tables below focus on where Collaborator and Guest stop.
Legend: ✓ allowed · Own company limited to their own company's records · Own limited to records they created · — not allowed.
Issues
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View issues | ✓ | ✓ | Own company |
| Create an issue | ✓ | ✓ | — |
| Edit an issue | ✓ | ✓ | — |
| Delete an issue | ✓ | ✓ | — |
| Change status | ✓ | ✓ | ✓ |
| Bulk assign / bulk update | ✓ | ✓ | — |
| View activity history | ✓ | ✓ | — |
| Add a comment | ✓ | ✓ | ✓ |
| Edit / delete a comment | ✓ | Own | Own |
| Add an attachment | ✓ | ✓ | ✓ |
| Edit / delete an attachment | ✓ | Own | Own |
A Guest can move an issue's status and respond with photos and comments — which is the whole point of inviting a subcontractor — but cannot create or delete issues.
Zones and unit lifecycle
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View zones | ✓ | ✓ | ✓ |
| Create a zone | ✓ | ✓ | — |
| Edit a zone | ✓ | ✓ | — |
| View unit lifecycle | ✓ | ✓ | ✓ |
| Change a unit's state | ✓ | ✓ | — |
Unit lifecycle changes deliberately mirror zone editing rather than being manager-only. Site managers are usually Collaborators, and routing every state change through one person would make handover a bottleneck.
Documents
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View public documents | ✓ | ✓ | ✓ |
| View documents shared with them | ✓ | ✓ | ✓ |
| Upload | ✓ | ✓ | — |
| Download | ✓ | ✓ | ✓ |
| Delete | ✓ | Own | — |
| Manage folders | ✓ | ✓ | — |
| Submit for review | ✓ | ✓ | — |
| Approve or reject | ✓ | — | — |
Checklists
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View templates | ✓ | ✓ | — |
| Create / edit / delete templates | ✓ | — | — |
| View checklist instances | ✓ | ✓ | ✓ |
| Create / edit / delete instances | ✓ | ✓ | — |
| Complete a checklist | ✓ | ✓ | — |
| Respond to items | ✓ | ✓ | ✓ |
Site meetings
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View meetings | ✓ | ✓ | ✓ |
| Open a meeting | ✓ | ✓ | — |
| Edit a meeting | ✓ | ✓ | — |
| Record attendance | ✓ | ✓ | — |
| Record progress | ✓ | ✓ | — |
| Publish a report | ✓ | — | — |
| Delete a meeting | ✓ | — | — |
| Manage meeting templates | ✓ | — | — |
| View points | ✓ | ✓ | Own company |
| Raise a point | ✓ | ✓ | — |
| Update a point | ✓ | ✓ | Own company |
| Comment on a point | ✓ | ✓ | ✓ |
A Collaborator runs the meeting; publishing stays with a Manager. A Guest reads published reports and updates the points their own company owns or is concerned by.
A Guest can update their own company's points but cannot hand a point to a different company — reassigning is a manager-level call, and a guest who could reassign could also move a point out of their own view in the same action.
Reports
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| Generate a report | ✓ | ✓ | — |
| Email a report | ✓ | ✓ | — |
| Manage report templates | ✓ | ✓ | — |
Companies and project settings
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View the project | ✓ | ✓ | ✓ |
| Archive the project | ✓ | ✓ | — |
| View companies | ✓ | ✓ | — |
| Manage companies | ✓ | — | — |
| Manage project members | ✓ | — | — |
| Customize the workflow | ✓ | — | — |
The organization admin override
An organization admin has full access to every project in the organization regardless of their project role — including projects they were never explicitly added to. The exception is subscription and plan management, which is not an organization-level power at all.