Set up permission templates

A permission template is a named set of access levels, one per tool. Each person on a project gets one. This page is the how-to; for the reasoning behind it, see Roles and permissions.

The four levels

Level	Allows
None	Nothing. This is the default for any tool a template doesn’t set.
Read Only	View
Standard	View, create, edit
Admin	View, create, edit, delete, and configure the tool

Company admins have Admin on every tool in every project, whatever template they’re assigned.

Starting templates

New trial workspaces come with Project Admin, Project Manager, Standard, Read Only and Subcontractor (Preview: these arrive with self-serve signup). Use them as they are, or treat them as a starting point.

Create or edit a template

Changes to a template apply right away to everyone assigned to it, on every project. Deleting a template clears its assignments, so those people drop to no access until you assign another.

You can also edit templates from inside a project: open the project’s Admin tool → Permissions, pick a template and edit its Permission Matrix, then Save Matrix. Editing shared templates there still needs a company admin.

Finer switches

The project Admin tool → Permissions also holds switches that go beyond the level for a few tools, for example:

• Tasks: who can view all tasks, change status, assign to standard users or close assigned tasks.
• RFIs: Act as RFI Manager, Mark Official Responses, and seeing private RFIs of people in the same company.
• Punch List and Transmittals: seeing (and for punch, responding to) private items of people in the same company.
• Daily Log: whether Standard users can edit and delete their own entries, and who can copy a log.
• Commitments and Prime Contracts: viewing private purchase orders and work orders, and creating, updating or deleting contracts.

Assign templates to people

Each person on a project has exactly one template there. Set it in either place:

• The project’s Directory tool: open the person and pick a Project Permissions Template.
• The project’s Admin tool → Permissions → User Permission Assignments: a list of everyone on the project with a template picker and Save.

To get someone onto a project in the first place, see Invite your team.

Turn tools on or off per project

Not every job uses every tool. In the project’s Admin tool → Tools, each tool shows Active or Inactive with a button to switch it. A disabled tool disappears from the project’s navigation and its API is blocked for that project. Admin, Directory, Activity and Notifications are core tools and can’t be turned off.

Common setups

• Keep financials private. Set Budget, Commitments, Prime Contracts, Change Orders, Change Events, Direct Costs and Payment Applications to None on every template except the ones for PMs, project executives and accounting.
• Field staff. Standard on Daily Log, Photos, Punch List, Observations, Inspections, Incidents, Timesheets and RFIs; Read Only on Drawings, Specifications and Schedule; None on financial tools.
• Subcontractors. Start from Subcontractor (Standard on RFIs, Submittals, Punch List; Read Only elsewhere) and set to None anything they shouldn’t read, usually the financial tools and internal correspondence.
• Owner’s reps. Read Only on the project management tools they follow, None on your internal cost tools.