Who can do what
The six workpack permissions, which roles hold them by default, and how approvers, outside reviewers, subcontractors and RFI assignees get their access.
Workpacks has six permissions. Each role holds a fixed set of them by default, and you can take them away from one person; see Adjust someone's access.
The permissions
| Permission | Lets a person |
|---|---|
| View workpacks | Open workpacks and templates, read them, and download their PDFs. Generating the plan PDF or a progress PDF is offered to your own team only, not to Field users, client users, suppliers or visitors. |
| Manage workpacks | Build and publish templates; start, edit, revise, clone, submit, close out, archive and delete workpacks; set up approvers; mark rows N/A; send reminders to finish rows; link subcontractors; raise, issue and close RFIs; manage print templates and settings. |
| Sign off workpacks | Sign off rows on site, capture records and photos, call witnesses, mark rows failed and close defects. |
| Approve workpacks | Listed with the others, but approving is decided by the approver chain (see below). |
| Override workpacks | Sign off a row that is blocked by a hold point or waiting for a witness, with a reason. |
| Override workpack status | Force a workpack to any status with Override status. |
Every other workpack permission includes View workpacks.
Who has them by default
| Role | View | Manage | Sign off | Approve | Override | Override status |
|---|---|---|---|---|---|---|
| Owner | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Admin | ✓ | ✓ | ✓ | ✓ | — | ✓ |
| Manager | ✓ | ✓ | ✓ | ✓ | — | — |
| Field | ✓ | — | ✓ | — | — | — |
| Customer (client users) | ✓ | — | — | — | — | — |
| Supplier | — | — | — | — | — | — |
Field users see only the workpacks with rows assigned to them, or on an order they are rostered to. They read the whole workpack but can act only on their own rows. Client users see only the workpacks they are asked to review.
Access that doesn't come from a role
- Approvers. Whoever is named on the current step of the approver chain can approve or reject; nobody else can, whatever their role. The one exception is approval cover: while an approver is away, the person covering for them can decide their step. See Get a workpack approved and Cover approvals while someone is away.
- Outside reviewers. An email approver joins your organization as a client user who can open only the workpacks they are asked to review. See Invite outside reviewers.
- Subcontractors. Members of a linked organization who can sign off workpacks in their own organization can act on the rows delegated to it, and only those. See Delegate to subcontractors.
- RFI assignees. Being asked is what lets someone answer, from the moment the RFI is issued. Nobody can answer for someone else, and Override workpacks doesn't change that. Field users and visitors can never be asked. See Raise an RFI.
- Ownership. The owner of a workpack can transfer it even without Manage workpacks. See Close out a workpack.
An organization set up from a principal contractor's invitation without its own subscription can sign off rows delegated to it, but can't create its own templates or workpacks; its screens show an Assignment-only plan banner. See Accept an invitation.
When someone can't…
- …see Workpacks at all: their role lacks View workpacks, or they are a Field user with nothing assigned.
- …see New workpack or New template: they need Manage workpacks.
- …sign off a row: the workpack must be Active; otherwise the execution screen says "Not open for sign-off". They need Sign off workpacks; a Field user must be the row's responsible party. A Blocked or Awaiting witness button needs the earlier row done, or Override workpacks. Complete required forms first means the row's required form isn't submitted yet.
- …approve: it isn't their step yet, or they aren't on the chain.
- …answer an RFI: they aren't on its list, it hasn't been issued, or they have already answered.