Section Permissions
Section permissions let blueprint designers restrict which contributor roles can view or edit individual sections of the blueprint. Use section permissions to separate commercially sensitive sections (contract financials, insurance, legal) from general operational sections, or to direct contributors to only the sections they are responsible for.
How section permissions work
By default, every contributor with access to an edition can view and edit all sections. When you configure section permissions on a section, only the roles listed as having access can view or edit that section.
Roles not listed in the section's permissions:
- Cannot see the section in the section navigation panel.
- Cannot access the section in form mode or grid mode.
- Cannot see data from that section in review or history views.
Admins and report owners always have full access to all sections regardless of section permissions.
Permission levels per section
| Permission level | What the role can do |
|---|---|
| No access | Section is hidden — the role cannot see it exists. |
| View | Can read the section data but cannot edit any fields. |
| Edit | Can view and edit all fields in the section. |
| Edit assigned only | Can edit only rows in the section where they are the assigned contributor (grid mode). |
Configuring section permissions
- Open the blueprint in the Blueprint Designer.
- In the Sections panel, click a section to open its settings.
- Click the Permissions tab.
- For each role, choose the permission level.
- Leave roles at No access to hide the section from them.
- Click Save section.
If all roles are left at the default (inherit), the section is visible to all contributors. You only need to configure permissions for sections that require restrictions.
Roles available for section permissions
The roles that appear in the permissions panel depend on the roles configured for the blueprint. Typical roles include:
| Role | Typical use |
|---|---|
| Admin | Always has full access; cannot be restricted at section level. |
| Report owner | Always has full access. |
| Reviewer | Can be restricted from editing financial or sensitive sections. |
| Contributor | Most common target for section-level restrictions. |
| Observer | Typically View-only; can be restricted to No access on sensitive sections. |
Custom roles defined for the blueprint workspace also appear in the permissions panel.
Section permissions in practice
Example: Commercial sections
| Section | Admin | Report owner | Commercial manager | Site manager | Observer |
|---|---|---|---|---|---|
| Schedule summary | Edit | Edit | View | Edit | View |
| Cost performance | Edit | Edit | Edit | No access | No access |
| Contract notices | Edit | Edit | Edit | No access | No access |
| Safety report | Edit | Edit | View | Edit | View |
Example: Multi-contributor section assignment
For a blueprint with one section per work package owner:
- Create one section per work package (WP-A, WP-B, WP-C).
- For each section, give the relevant work package lead Edit access.
- Give all other contributors No access.
- Give the report owner and reviewers View or Edit.
This ensures each contributor sees and fills only their section.
Output designer and section permissions
Section permissions apply during edition data entry only. In the Output Designer, all sections and their field bindings are visible to the blueprint designer regardless of section permissions. This allows designers to create outputs that pull data from restricted sections (e.g. a cost waterfall chart from the commercial section).
When a report is published, the output renders with all data. The report viewer applies a separate set of output permissions (not section permissions).
Audit and visibility
- The section permission configuration is visible to Admins and report owners in the Blueprint Designer.
- Contributors do not see which sections exist that they don't have access to.
- The edition history log records field-level changes but does not expose restricted sections to roles without access.