Skip to main content

What is a permissions template?


In Procore, a permissions template is a set of permissions that can be assigned to one or more Procore users. The settings in a permissions template define what actions users can perform and what information they can view in each Procore tool.

There are two types of permissions templates:

Both Project and Company level permission templates are created and edited in the Company level Permissions tool. Project-specific permissions templates can also be created in the Project level Directory tool, but after creation, can only be edited in the company's Permissions tool.

To learn how to created, edit and assign permission templates, see Manage Project Permissions Templates and Manage Company Permissions Templates.

When a company licences Procore and starts setting up their account, a set of default project permissions templates is provided that is specific to the type of work your company does (for example, general contracting or subcontracting). To learn what default templates are provided, see What are the default project permissions templates in Procore?

Why do I need different permission templates for Company level and Project level tools?

Company level tool permissions are managed separately from Project level tool permissions because they allow users to interact with tools that are not specific to a given project. There is only one of each company level tool available in a company's Procore account.

Some company level tools are repeated at the project level for different purposes. For example, the Company level Directory tool is used to manage all user accounts, regardless of which projects those users are working on. The Project level Directory tool allows you to manage which users have access to a specific project and its tools.

A project level tool helps users manage project-specific data and processes. Each project will have its own unique set of project tools.

For example, you might use the RFIs tool on several projects, but since each project's RFIs list is unique, each project will have its own unique RFIs tool. As a best practice, you'll give access to a project's RFIs tool to only the users who are working on RFIs for that project.