User Permissions Matrix - Web
The following reference page is a comprehensive breakdown of all user actions and the specific user permissions (Read Only, Standard, and/or Admin) that are required to be able to perform that action. Since certain tools are available at both the Company and Project levels, be sure to select the appropriate navigational hyperlink below.
Company Level
Admin
The following table highlights which user permissions are required to perform the described user action.
* The user must have 'Admin' level permissions on both the Company and Project level Admin tools.
Directory
The following table highlights which user permissions are required to perform the described user action.
+ - Indicates that the task can be completed if the user is granted the correct Granular Permissions. See Grant Granular Permissions in a Company Permissions Template
Important
A user who is granted 'Admin' permissions on the Company level Directory tool is automatically granted 'Admin' permissions across all Project level tools and all Company level tools (except for the Permissions tool).1 A user with 'Standard' level permission must also be granted the 'Request Company and People Imports' granular permission. See Grant Granular Permissions in a Project Permissions Template and Request Company and User Imports.
2 The template is designed for use with Microsoft Excel. Although not recommended, you may be able to use a spreadsheet program that is compatible with the XLSX format. A user with 'Admin' level permission or a user with 'Standard' level permission plus the 'Request Company and People Imports' granular permission can download the template from the Procore web application. See Download the Company or User Import Template.
Documents
The following table highlights which user permissions are required to perform the described user action.
1 Users with 'Standard' level permissions can only check in a file that they have checked out.
2 Users with 'Read Only' or 'Standard' level permissions can only access 'Private' files and folders if they have been granted access to the file or folder.
3 Search results will only include the documents the user performing the search has access to.
Equipment
The following table highlights which user permissions are required to perform the described user action.
1 Users with 'Standard' permission can only perform the task on the equipment entries they create.
ERP Integrations
Integration by Procore | Integration by Ryvit | Sage 100 Contractor | Sage 300 CRE | QuickBooks
Sage 100 Contractor
Company Level Inspections
The following table highlights which user permissions are required to perform the described user action.
Permissions
The following table highlights which user permissions are required to perform the described user action.
1 Users with the appropriate permissions can assign company permissions templates to users in the Company level Directory tool when creating or editing a user account. See Add a User Account to the Company Directory and Edit a User Account in the Company Directory.
2 Users with the appropriate permissions on the Company level Directory tool can assign a default project permissions template to a user when creating or editing the user's Directory record. See Add a User Account to the Company Directory and Edit a User Account in the Company Directory.
3 Users with the appropriate permissions on the Company level Directory or Project level Directory tools can change a user's project permissions template on a specific project when adding the user to a project or editing the user's Directory records. See Add a User Account to the Project Directory, Edit a User Account in the Company Directory, and Edit a User Account in the Project Directory.
4 Users with the appropriate permissions can create project specific permission templates in the Project level Directory tool. See Create a Project Permissions Template from the Project Directory.
Planroom
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Configure Advanced Settings: Planroom | |
|||
| Download Tender Documents | * | |
|
|
| Reading Your Tender Package | * | |
|
|
| Submit a Tender | * | |
|
|
| View All Tender Packages in the Company | |
|||
| View Tender Package (that they have access to) | * | |
|
|
| View the Planroom Tool | * | |
|
|
*Tenderers need to be added to the Company level Directory in order for you to invite them to tender on a project. Once they are invited to tender, tenderers will automatically be given access to the Planroom. Project managers will not need to give them access manually.
Portfolio
The following table highlights which user permissions are required to perform the described user action.
1 This task requires 'Admin' level permissions on the Company level Directory tool, or 'Read Only' or higher on the company's Portfolio tool with the privilege to create new projects. See Allow Users to Create New Projects.
2 Only users who were added to the Project level Directory for one or more inactive projects can view those inactive projects in the company's Portfolio tool.
Prequalification Portal
The following table highlights which user permissions are required to perform the described user action.
Note: Users will only have access to prequalification forms that they have been invited to collaborate on.
Users need to be added to the Company level Directory in order for you to invite them to prequalify. Once they are invited to prequalify, they will automatically be given 'Read Only' permissions on the Prequalification Portal tool.
Prequalifications
The following table highlights which user permissions are required to perform the described user action.
Users need to be added to the Company level Directory in order for you to invite them to prequalify. Once they are invited to prequalify, they will automatically be given 'Read Only' permissions on the Prequalification Portal tool.
1 'Standard' level users can view all categories response data except for Financials.
2 'Standard' or 'Admin' level permissions are required on the company's Directory tool to complete this function.
3 'Standard' level users can perform functions on items they have created.
Reports
The following table highlights which user permissions are required to perform the described user action.
1 This task can only be completed by the report's creator.
2 Report-specific permissions may apply.
3 This task can be completed by users with access to the report as its creator or a viewer (if shared).
4 This task can only be completed by the creator of a report's visuals.
5 The Company Level Open Submittals Report must be enabled on the backend by Procore.
6 This task can only be completed by the dashboard's creator.
Timecard
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Configure Advanced Settings: Timecard | |
|||
| Configure Your Company For The Timecard | |
|||
| Create a Timecard Entry 1 | |
|
||
| Edit a Timecard Entry 1 | * |
|
||
| Export a Timecards Report | |
|||
| Delete a Timecard Entry 1 | * |
|
||
| View the Change History of a Timecard Entry | |
|||
| View Timecard Entries | |
|||
| View Your Own Timecard Entries | |
|
|
1 Users with 'Standard' level permissions can only create, edit, and delete their own timecard entries.
Timesheets
The following table highlights which user permissions are required to perform the described user action.
1 'Admin' users on the project's Timesheets tool can perform functions on all time entries.
2 'Standard' users on the project's Timesheets tool can perform functions on time entries that they have created.
3 'Admin' level permissions are required on QuickBooks® Desktop to complete this function.
Project Level
Admin
The following table highlights which user permissions are required to perform the described user action.
+ - Indicates that the task can be completed if the user is granted the correct Granular Permissions. See Grant Granular Permissions in a Permission Template.
1 You must have 'Admin' permissions to the Project level tool that you want to extract data from.
2 The Project level Timesheets tool must also be enabled.
3 The Project level Admin tool's Permissions Table page only allows permissions to be changed for users who do not have a permission template assigned to them and are not Company level Admins. All other permissions must be managed in the Project and Company Level Directory tools.
Budget
The following table highlights which user permissions are required to perform the described user action.
+ - Indicates that the action can be completed if the user is granted the appropriate granular permissions. See Grant Granular Permissions in a Permission Template.
- Indicates your company's Procore account must be configured to work with an integrated ERP system.
1 This task was designed for use in Australia and New Zealand. It also requires 'Admin' permissions on the project's Head Contracts tool.
2 Also requires 'Admin' permissions on the Company level Reports tool.
3 These steps require that your company has enabled the ProEst by Procore integration.
4 The Reports tool must be an active Project Tool. See Add and Remove Project Tools.
Change Events
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action that is supported by Procore for Android or Procore for iOS.
1 These tasks also require additional permissions on other tools in Procore. For more information, view the "Things to Consider" section in the tutorial for that action.
2 Users with 'Standard' permission can only delete the change events they create.
3 Users with 'Standard' permission can only edit the change events they create.
Commitments
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action that is supported in Procore's iOS and/or Android mobile application.
+ - Indicates that the action can be completed if the user is granted the appropriate granular permissions. See Grant Granular Permissions in a Permission Template.
- Indicates your company's Procore account must be configured to work with an integrated ERP system.
1 Users must have 'Standard' permissions on the project's Commitments tool. Users must also be added to the Private drop-down list for that commitment or must be designated as an Invoice Contact. See Add Invoice Contacts to a Commitment.
2 Also requires a DocuSign© account.
3 Users with 'Admin' permission can configure the 'Enable Purchase Orders' setting to provides Procore users with 'Standard' permission with the ability to create variations. For details, see Configure Settings: Commitments.
4 Users must have 'Read-Only' or 'Standard' permissions on the project's Commitments tool. Users must also be added to the Private drop-down list for that commitment or must be designated as an Invoice Contact. See Add Invoice Contacts to a Commitment.
5 Commitments synced with an integrated ERP system cannot be deleted until they are unlinked. See Delete a Commitment Synced with QuickBooks® and Delete a Commitment Synced with Sage 300 CRE®.
6 Users with 'Admin' permissions on the project's Commitments tool can export a commitment as either a PDF or a DOCX file. Users with 'Standard' or 'Read-Only' permissions on the project's Commitments tool can export a commitment as a PDF if they have been granted access via the privacy drop-down menu when editing or creating a commitment.
7 Users with 'Read-Only' permissions on the Commitments tool can perform these procedures if they are also listed in the Private field under the commitment's General tab.
8 Users with 'Read only' and 'Standard' permission (and who have NOT been assigned the granular permission detailed in the table) must also be a member of the 'Private' list.
9 Also requires 'Standard' or 'Admin' permission on the project's Change Events tool.
10 Individual report availability depend on your permission level. See View Reports in the Commitments Tool.
Coordination Issues
The following table highlights which user permissions are required to perform the described user action.
1 Users will also need 'Standard' or 'Admin' permissions on the RFIs tool.
2 'Standard' users can only edit, reopen and delete coordination issues that they created.
3 'Standard' users can only mark a coordination issue as complete if they are listed as the Assignee.
4 Users can only edit or delete comments that they have added.
5 Users can only reassign a co-ordination issue to another user if they are currently listed as the Assignee on the issue. However, 'Admin' users can change the assignee for a co-ordination issue by editing the Assignee field on the issue. See Edit a Co-ordination Issue.
6 Users will also need 'Standard' or 'Admin' permissions to the project's Observations tool.
Direct Costs
The following table highlights which user permissions are required to perform the described user action.
+ - Indicates that the task can be completed if the user is granted the correct Granular Permissions. See Grant Granular Permissions in a Permission Template.
Directory
The following table highlights which user permissions are required to perform the described user action.
Important! A user who is granted 'Admin' level permissions to the project's Directory tool is also automatically granted 'Admin' permissions across all of the project's tools.
- Denotes an action that is supported in Procore's iOS and/or Android mobile application.
+ - Indicates that the task can be completed if the user is granted the correct Granular Permissions. See Grant Granular Permissions in a Project Permissions Template.
Documents
The following table highlights which user permissions are required to perform the described user action.
- Indicates an action supported in Procore's iOS and/or Android mobile application.
+ - Indicates that the action can be completed if the user is granted the appropriate granular permissions. See Grant Granular Permissions in a Permission Template.
Drawings
The following table highlights which user permissions are required to perform the described user action.
- Indicates an action supported in Procore's iOS and/or Android mobile application.
+ - Indicates that the action can be completed if the user is granted the appropriate granular permissions. See Grant Granular Permissions in a Permission Template.
1 Users must also have 'Read Only' or higher permissions on the project's Photos tool.
2 Only users with 'Admin' permissions can subscribe or unsubscribe other users to the Drawings tool.
3 Users can only see their own measurements that they have added to drawings using the measurement markup tools. See Add Measurements to a Drawing.
Emails
The following table highlights which user permissions are required to perform the described user action.
1 Users with 'Standard' permissions to the Emails tool can make an email private or public if they created it.
2 Anyone who knows the exact inbound email address for the project can send an email to the Emails tool, regardless of whether they are a project user in Procore. See Send An Inbound Email to the Project's Emails Tool.
3 The ability to set up an email signature is available under your name in the upper right corner of the Procore web application under 'My Settings'.
4 Procore permissions are not required for a person to reply to an email using an email client outside of Procore. However, only 'Standard' and 'Admin' level users can use the reply function within the Emails tool in Procore.
Equipment
The following table highlights which user permissions are required to perform the described user action.
Note: Users will need 'Read-only' or above permissions on the Company level Equipment tool to access the Project level Equipment tool.
- Denotes an action supported in Procore's iOS and/or Android mobile application.
1 'Standard' users can perform functions on equipment entries they have created.
Forms
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action supported in Procore's iOS and/or Android mobile application.
Forms Tool
1 'Standard' users can view forms marked as private that they have created.
Admin Tool (Company Level)
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Create a Company Level Form Template | |
|||
| Delete a Company Level Form Template | |
Home
The following table highlights which user permissions are required to perform the described user action.
Note: Users with 'Admin' permission to the project's Home tool can send announcements from Procore's mobile app on iOS and Android. See Announcements.
Incidents
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action that is supported in Procore's iOS and/or Android mobile application.
1 'Standard' users can edit assets in incidents that they create.
2 'Standard' users can only email incidents that they create.
Inspections
The following table highlights which user permissions are required to perform the described user action.
Note: If a user has 'Read-only' or 'Standard' permissions on the Inspections tool, they will not be able to view a private inspection unless they have been added to the distribution list or added as an Inspector or Point of Contact on the inspection. This also affects the user's ability to see observations created from the inspection, even if the observations are assigned to the user.
- Denotes an action supported in Procore's iOS and/or Android mobile application.
1 'Read only' and 'Standard' level users can view related items. 'Admin' users can add related items.
2 'Standard' level users can only close and edit inspections that they have created.
3 'Standard' level permission or higher is also required on the Observations Tool to complete this function.
Instructions
The following table highlights which user permissions are required to perform the described user action.
1 You must also be your company's Procore Administrator.
2 You must also have permissions to the RFI tool. See Create an Instruction from an RFI.
3 Users with 'Standard' permissions can only edit instructions that they have created.
Invoicing
User access to the Invoicing tool depends on the user's access permission to the contract in the Head Contracts and/or Commitments tool. The tables below highlight which permissions are required for each tool in order to perform specific tasks with the Invoicing tool.
Invoicing
| Job Role | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Create Automatic Billing Periods | 1 |
|||
| Create Manual Billing Periods | 1 |
1 To perform this task in the project's Invoicing tool, users must be granted 'Admin' level permissions on the project's Commitments tool.
Head Contracts
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Create Payment | |
|||
| Create an Owner Progress Claim | |
|||
| Edit an Owner Progress Claim's Configurable PDF View | |
|||
| Email an Owner Progress Claim | |
Commitments
The following table highlights which user permissions are required to perform the described user action with the Invoicing tool.
1 To perform this task, users must have 'Read Only' or 'Standard' permission on the project's Commitments tool. Users must also be added to the Private drop-down list for the commitment or be designated as the Invoice Contact on the commitment. See Add Invoice Contacts to a Commitment.
2 To perform this task, users must have 'Standard' permission on the project's Commitments tool or be designated as an invoice contact on the commitment. See Add Invoice Contacts to a Commitment.
3 To perform this task and to release retainage during the current billing period, users must have 'Standard' permission on the project's Commitments tool or be designated as an invoice contact on the commitment. See Add Invoice Contacts to a Commitment. To set retainage, you must be a user with 'Admin' level permissions on the Commitments tool.
4 To perform this task, you must have the permissions designated in the tutorial, and your user account must be designated as an invoice contact on the purchase order or subcontract.
5 To perform this task, you must have the permissions designated in the tutorial, and your user account must be designated as an invoice contact on the purchase order or subcontract. 'Read Only' users must be added to the 'Private' list.
Meetings
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action supported in Procore's iOS and/or Android mobile application.
1 Any person (even non-Procore users) with the email address for the meeting can initiate a communication thread. See Initiate an Email Communication Thread for a Meeting.
Models
The following table highlights which user permissions are required to perform the described user action.
1 'Standard' permission does not exist for the Models tool.
2 Users will need 'Read-only' or higher permissions to the Drawings tool to map a 2D sheet to a model.
Observations
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action supported in Procore's iOS and/or Android mobile application.