Yes. For special use cases where you want to restrict a Procore users' ability to perform tasks associated with 'Standard' or 'Admin' level permissions on a Procore tool, your company's Procore Administrator can use Procore's granular permissions feature to create role-based permissions templates. You can then assign that permission template to the desired user(s) on your project.
The table below includes a list of the Company level tools that support granular permissions. These granular permissions can be granted to users through new or existing company permissions templates.
Tool | Link to Available Granular Permissions |
---|---|
Tender Board/Portfolio Planning | What granular permissions are available for the company's Tender Board tool? |
Directory | What granular permissions are available for the Company level Directory tool? |
Workflows |
What granular permissions are available for the company's Workflows tool? |
The table below includes a list of the Project level tools that support granular permissions. These granular permissions can be granted to users through new or existing project permissions templates.
1 The Client Contracts tool is only available to Procore users in the United States who have implemented the Procore for Speciality Contractors point-of-view dictionary. See What tool names and terms are different in Procore for main contractors, owners and speciality contractors?
2 The Funding tool is only available to Procore users in the United States who have implemented the Procore for Owners point-of-view dictionary. See What tool names and terms are different in Procore for main contractors, owners and speciality contractors?
The table below describes some examples of common use cases that can be addressed using granular permissions. See Grant Granular Permissions in a Permission Template.
Tool | Example Use Case | Recommended Solution |
---|---|---|
Admin | I want to provide a trusted accountant with permission to create, edit and delete cost codes for a Procore project. | Create a new permission for the role. Assign the template the Manage Cost Codes granular permission. Then assign that template to the user on the project to apply the changes. See Manage Permission Templates. |
Tendering | I want to provide an internal user with permission to create, edit and delete tender notes on a tender package. However, I don't want that user to have permission to perform the other tasks associated with the default 'Standard' or 'Admin' level permission on the project's Tendering Tool. | Create a new permission template for the role. Assign that template the Create Tender Notes, Edit Tender Notes and Delete Tender Notes granular permissions. Then assign that template to the user on the project to apply the changes. See Manage Permission Templates. |
Commitments | We hired a few temporary employees who will help us create and update purchase orders and subcontracts on our project. However, we do not want to grant those users 'Standard' or 'Admin' level permission to the Commitments tool because we do not want them to be able to delete commitments or create variation requests on the project. | Create a new permission template for the role. Assign that template the Create Purchase Order Contract, Create Work Order Subcontract, Update Purchase Order Contract and Update Work Order Contract granular permissions. Then assign that template to the user on the project to apply the changes. See Manage Permission Templates. |
Site Diary | I have a subcontractor who will act as an external collaborator on a construction project's Site Diary tool. | Create a new permission template for the external collaborator(s). Assign that template the 'Allow Subcontractor Entry' granular permission. Then assign that template to the user on the project to apply the changes. See Manage Permission Templates. |
Directory | I need to grant permissions to a trusted user so that they can create and edit user records, company records and distribution groups on the Project Directory. However, I do not want to grant this user 'Admin' level permissions on the Project Directory because I do not want this user to have full 'Admin' level permissions for the Project Directory and all project tools. I want to limit this user's permissions on the Project Directory to only be allowed to create and edit users, companies and distribution groups. | Create a new permission template for the role. Assign that template the Add from Company Directory (Assignable Permission Templates Only), Create and Edit Users, Create and Edit Companies, and Create and Edit Distribution Groups granular permissions. Then assign that template to the user on the project to apply the changes. See Manage Permission Templates. |
Documents | I would like to provide our project's administrative coordinator with limited access permissions to move, copy and rename files and folders in the Documents tool. However, I do not want to provide that user with 'Standard' or 'Admin' level permissions to the Documents tool because I do not want them to be able to delete, upload or replace any files or folders. | Create a new permission template for the role. Assign that template the Move and Copy Files and Folders and Rename Folders and Files granular permissions. Then assign that template to the user on the project to apply the changes. See Manage Permission Templates. |
Snag List | I would like to provide my employees with the ability to view snag list items that are assigned to other users at our company, so they can respond when the assignee is absent. | Create a new permission template for that role. Assign the template the Respond to Snag Items Assigned to Users within the Same Company. Then assign that template to the users on that project who work at the desired company. See Manage Permission Templates. |