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 (Company Level)
The following table highlights which user permissions are required to perform the described user action.
- Indicates that the task can only be completed when Procore is configured to use the Company level ERP Integrations tool. See ERP Integrations.
* The user must have 'Admin' level permissions on both the Company and Project level Admin tools.
Bid Board
The following table highlights which user permissions are required to perform the described user action.
1 Users with the 'Create New Projects' privilege in Procore can also add projects to the Portfolio tool. See Allow Users to Create New Projects.
2 Users with 'Read Only' and 'Standard' level permissions can only view projects that they are marked as an 'Estimator' for, unless they have the 'Can Access Projects for All Users' granular permission enabled on their permission template.
Conversations (Beta)
The following table highlights which user permissions are required to perform the described user action.
Note: The Conversations tool does not have its own set of permissions to assign, and instead relies on users being part of a project's Directory and having access to items within that project. See the notes below the table for specific considerations.
1 The permission required for creating and managing a group depends on the 'Group Conversations Permissions' setting in the Company level Admin tool of the Procore account. See Configure Access and Settings for the Conversations Tool.
- If 'Administrators' is selected, 'Admin' level permissions to the Project or Company level Directory tool.
- If 'Internal Employees' is selected, users who are marked as internal employees. See How do I add someone as an employee of my company?
- If 'Everyone' is selected, any user in the Company Directory.
2 This action can be performed by any user in the project's Directory (for their own conversations and items that they have access to). See the specific considerations below:
- Direct Messages:
- If Direct Messages are enabled for the account, anyone in the project's Directory (and Company Admins) can be messaged or mentioned.
- If Direct Messages are only enabled for internal employees, only users marked as employees of the company can be messaged or mentioned. See How do I add someone as an employee of my company?
- Direct messages are private and can only be seen by the individuals in the message. Admin users cannot view direct messages that they are not a part of.
Note: A data export containing direct messages can be provided to Company Admins by Procore Support if needed.
- Group Conversations:
- Anyone in the project's Directory (and Company Admins) can be messaged or mentioned in a group.
- Messages within a group conversation can only be seen by members of that group.
- Item Conversations:
- Conversations for specific items in a project can only be viewed and participated in by users with access to the item in Procore ('Read Only' or higher permissions to the item's tool, and appropriate access if an item is marked as Private).
- All conversations:
- Users can only message or mention users who exist in the project's Directory, as well as Company Admins.
- Users can only edit and delete their own messages (within 5 minutes of sending, and if the feature is enabled).
- Users can only hide a conversation from their own view.
Cost Catalog
The following table highlights which user permissions are required to perform the described user action.
Documents (Company Level)
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.
ERP Integrations
Integration by Procore | Integration by Ryvit | Sage 100 Contractor | Sage 300 CRE | QuickBooks
Sage 100 Contractor
Inspections (Company Level)
The following table highlights which user permissions are required to perform the described user action.
Planroom
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Check the Status of your Bid |  1 |
|
|
|
| Configure Advanced Settings: Planroom | 1 |
|
|
|
| Download Bid Documents | 1 |
|
|
|
| Indicate your Intention to Bid | 1 |
|
|
|
| Submit a Bid | 1 |
|
|
|
| Submit a Pre-Bid Question | 1 |
|
|
|
| Update a Submitted Bid | 1 |
|
|
|
| View a bid package you have been invited to | 1 |
|
|
|
| View the Planroom tool | |
|
|
1 Bidders must be added to the Company level Directory in order for you to invite them to bid on a project. Once a company is added to a bid package, bidders within that company will automatically be given access to the Planroom upon logging into Procore.
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.
Programs
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Add Programs | * |
|||
| Add a Project to a Program | * |
|||
| Assign a Project to a Different Program | * |
|||
| Delete a Program | * |
|||
| Edit Program Information | * |
|||
| Remove a Project from a Program | * |
|||
| View Programs | |
|
|
* These actions require the displayed permissions on either the Company or Project level Admin tool.
Reports (Company Level)
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.
Schedule (Company Level)
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Configure Advanced Settings: Company Level Schedule | |
|||
| Search Project Schedules | |
|
|
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 1 | |
|
||
| Edit a Timecard 1 | |
|
||
| Export a Timecards Report | |
|||
| Delete a Timecard 1 | |
|
||
| View the Change History of a Timecard | |
|||
| View a Timecard 1,2 | |
|
|
1 Users with 'Standard' level permissions can view, create, edit, and delete their own timecards.
2 Users with 'Read Only' level permissions can only view their own timecards.
Timesheets (Company Level)
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.
4 'Admin' level permissions are required on Sage 300 CRE® Desktop to complete this function.
5 Transferring time entries from Procore does NOT require the Procore + QuickBooks® Connector and/or Procore + Sage 300 CRE® Connector.
6 'Admin' users on the Company's Timesheets tool who have been added to the project can perform functions.
7 'Admin' users on the Company's Timesheets tool can perform functions on all time entries.
Workforce Planning
To access the Workforce Planning tool, users must have 'Read Only' permissions or higher for the Workforce Planning tool in the Company level directory. Their ability to take actions within the Workforce Planning tool are managed by these additional granular permissions.
Project Level
Bidding
The following table highlights which user permissions are required to perform the described user action.
1 Users must also have 'Admin' level permission to the Project level Directory tool to complete this function.
Note: In projects updated to Bid Management Enhanced Experience, this action can also be performed by users with 'Read Only' or higher permissions to the Project level Directory tool with the 'Create and Edit Companies' AND 'Create and Edit Users' granular permissions.
2 Users with 'Standard' level permission can view Bid Notes by default.
3 Users must also have 'Read Only' or higher permissions to the Documents, Drawings, or Specifications tools. Users can only view and update items that they have access to.
4 Users with 'Read Only' or higher level permissions to the project's Bidding tool AND added to the Bidding CC Group can complete this function.
5 These tasks are performed by bidders using the Company level Planroom tool. See Planroom.
Change Orders
The following table highlights which user permissions are required to perform the described user action.
1 To perform this task as a user with 'Standard' level permissions on the Change Orders tool, you must be the 'Designated Reviewer' on the change order. See Create a Commitment Change Order.
2 Users with 'Admin' level permissions on the project's Change Orders tool must be granted additional tool permissions: (1) To edit a Commitment Change Order (CCO), 'Admin' level permissions on the project's Commitments tool, and/or (2) to edit a Prime Contract Change Order (PCCO), 'Admin' level permissions on the project's Prime Contracts tool. Additional factors may also apply. For details, see Edit a Change Order.
3 Users with 'Read Only' or 'Standard' level permissions on the project's Change Orders tool can view change orders for contracts not marked 'Private.' If a contract is marked 'Private,' users must be added to the 'Private' drop-down list on the contract.
4 Users with 'Admin' level permissions to the project's Change Orders tool can also view change orders for contracts not marked 'Private'. If a contract is marked 'Private', users either be (A) added to the 'Private' drop-down list on the contract or (B) assigned 'Admin' level permissions on the Commitments and/or Prime Contracts tool.
Admin Tool
The following table highlights which user permissions are required in the project's Admin tool to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Enable the Change Orders 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 coordination issue to another user if they are currently listed as the Assignee on the issue. However, 'Admin' users can change the assignee for a coordination issue by editing the Assignee field on the issue. See Edit a Coordination Issue.
6 Users will also need 'Standard' or 'Admin' permissions to the project's Observations tool.
Crews
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.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Add a Worker 1, 2 |
|
|
||
| Create a Crew |
|
|
||
| Delete a Crew | |
|||
| Edit a Crew 2 |
|
|
||
| Edit a Worker 1 |
|
|||
| Remove a Worker 3 | |
|||
| Search Crews | |
|
|
|
| Search for a Worker | |
|
|
|
| View a Crew |
|
|
|
|
| View a Worker |
|
|
|
1 Users must also be granted 'Read Only' or 'Standard' level permissions on the Project level Directory tool with the 'Create Contacts' granular permission enabled on their permission template OR must be granted 'Admin' level permissions on the Project level Directory tool to perform this task.
2 Users with 'Standard' permission can only edit a crew when designated as the 'Crew Lead'. See Create a Crew.
3 'Admin' users must also be granted 'Admin' permission on the project's Directory tool to perform this task.
Direct Costs
The following table highlights which user permissions are required to perform the described user action.
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.
Estimating
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Add 3D Model Takeoffs | |
|
||
| Add an Estimate | |
|
||
| Add Area or Volume Takeoffs | |
|
||
| Add Count Takeoffs | |
|
||
| Add Linear Takeoffs | |
|
||
| Add Takeoffs | |
|
||
| Configure Settings: Estimating | |
|||
| Export a Bid | |
|
|
|
| Generate Bid Estimates | |
|
||
| Manage Takeoffs | |
|
||
| Set the Drawing Scale for Takeoffs | |
|
||
| View an Estimate | |
|
|
|
| View the Bid | |
|
|
|
| View Takeoffs | |
|
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.
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 access to the RFI and 'Read Only' level permissions or higher on the project's RFIs tool.
3 Users with 'Standard' permissions can only edit instructions that they have created.
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.
1 Company level Observation Types are managed at the Company level Admin tool. See Permissions.
2 When a 'Standard' user is the creator of an observation line item, the user will have the ability to change the status, close, and leave a comment. When a 'Standard' user is the assignee, the user can change the status to Initiated or Ready for Review. When a 'Standard' user is not the assignee on an observation, that user can view the activity stream and leave a comment. However, that user cannot view or change the status options.
3 'Standard' users can only assign observations to an 'Admin' user unless they have been granted the granular permission 'Can Assign Standard Users to Observations', which allows them to assign observations to another 'Standard' user.
4 'Standard' users can edit observations they have created.
5 'Read only' users can view observations that are not marked private. 'Read only' users can view private observations if included on the distribution list.
6 'Standard' users can view observations if they created the item or if the item is not marked private. 'Standard' users can view private observations if they created the item, set as the assignee, or are on the distribution list.
7 'Standard' users will also need 'Standard' permission to the Inspections tool.
Reports (Project Level)
Permissions are separated into Custom Reports and Enhanced Reporting sections
Custom Reports
The following table highlights which user permissions are required to perform the described user action.
| General Tasks | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Add a Visual to Custom Reports | |
|||
| Configure Advanced Settings: Reports | |
|||
| Create a Custom Project Report | 1 |
1 |
||
| Delete a Custom Project Report | 2 |
2 |
||
| Share a Custom Project Report | |
| Project Reports | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| View Cost Code Report | 3 |
3 |
3 |
|
| View Assignment Report | |
|||
| View User Sessions Reports | 3 |
|||
| View Outbound Emails Report | |
|||
| View RFI Delays | 3 |
3 |
3 |
|
| View Submittal Approvers' Response Time | 3 |
3 |
3 |
|
| View Punch List Delays | 3 |
3 |
3 |
|
| View Vendor Insurance Report | 4 |
4 |
4 |
|
| View Watch Folders Report | 3 |
3 |
3 |
|
| View Labor Budget to Actual Report | 3 |
3 |
3 |
|
| View Field Production Report | 3 |
3 |
3 |
|
| View Timecard Reports | 3 |
3 |
3 |
| Financial Reports | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Create a Custom Financial Line Items Report to Compare Budget Snapshots | |
|||
| View Budget Modifications Report | 5 |
5 |
5 |
|
| View Budget Detail Report | 5 |
5 |
5 |
|
| View Buyout Summary Report | 6 |
6 |
6 |
|
| View Overdue Prime Contract Change Orders | |
|
|
|
| View Committed Cost Report | |
|
|
|
| View Overdue Commitment Change Orders | |
|
|
|
| View Subcontractor Invoices by Date | |
|
|
|
| View Unexecuted Prime Contract Change Orders | |
|
|
|
| View Prime Potential Change Order Report By Change Reason | |
|
|
|
| View Monitored Resources Report | 5 |
5 |
5 |
| Schedule Reports | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| View All Schedule Reports | |
|
|
| Daily Log Reports | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| View All Daily Log Reports | |
|
|
1 To create a custom report, user with 'Standard' permission on the project's Reports tool also need 'Read-only' or higher permissions to the tools they want to create a report for. For Financial Management tools, users must have 'Admin' permission on the appropriate financial tool to create a custom report. For the Company Directory, users will need 'Admin' permission on the Company Directory.
2 Users can only delete the reports they created.
3 To view project reports, users may also need additional permissions on the project tool associated with the report data. See View a Report.
4 Users also need 'Admin' level permissions on the Project level Directory tool OR 'Read Only' or 'Standard' level permissions on the Project level Directory tool with the 'View Company Insurance Information' granular permission enabled on their permissions template to view this report.
5 To view budget reports, users also need 'Read Only' permissions or higher on the project's Budget tool. See View Budget Reports.
6 To view the 'Buyout Summary Report', users also need 'Read Only' permissions or higher on the project's Budget and Commitments tools. See View Budget Reports.
Enhanced Reporting
The following table highlights which user permissions are required to perform the described user action.
| General Tasks | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| View a Report | |
|
|
|
| Create a Report | |
|
||
| Edit a Report | |
|
||
| Delete a Report | |
|
||
| Share a Report | |
|
||
| Export a Report | |
|
||
| Distribute a Report | |
|
||
| Clone a Report | |
|
In addition, Depending on the field group, users may need additional permissions on the data's source tool in order to access the reportable data from within the Project level Reports tool. The table below shows each Enhanced Reporting field group's source tool (if applicable) and the permissions required on the source tool to access the reportable data.
| Field Group | Source Tool | None | Read Only | Standard | Admin |
|---|---|---|---|---|---|
| Actual Production Quantities | Budget OR Timesheets | |
|
|
|
| Budget Change Adjustment Line Items | Budget | |
|
|
|
| Budget Changes | Budget | |
|
|
|
| Budget Code | N/A | |
|
|
|
| Budget Line Item | Budget | |
|
|
|
| Budget Modification | Budget | |
|
|
|
| Budget Workflow Responses | Budget | |
|||
| Budget Workflow Steps | Budget | |
|||
| Budgeted Production Quantities |
Budget OR Timesheets |
|
|
|
|
| Change Event | Change events | |
|
|
|
| Change Event Line Item | Change events | |
|
|
|
| Change Event Production Quantity | Change events | |
|
|
|
| Commitment | Commitments | |
|||
| Commitment Change Order | Commitments | |
|||
| Commitment Change Order Line Item | Commitments | |
|||
| Commitment Change Order Markup | Commitments | |
|||
| Commitment Change Order Request | Commitments | |
|||
| Commitment Change Order workflow Responses | Commitments | |
|||
| Commitment Change Order workflow steps | Commitments | |
|||
| Commitment Line Item | Commitments | |
|||
| Commitment Potential Change Order | Commitments | |
|||
| Commitment Workflow Responses | Commitments | |
|||
| Commitment Workflow Steps | Commitments | |
|||
| Company (Vendor) - used in company reporting | N/A | |
|
|
|
| Company (Vendor) - used in project reporting | N/A | |
|
|
|
| Company Global Insurance | Directory | |
|
|
|
| Company Project Insurance | Directory | |
|
|
|
| Crew | Crews | |
|
|
|
| Direct Cost | Direct costs | |
|
|
|
| Direct Cost Line Item | Direct costs | |
|
|
|
| Distribution List | RFI | |
|||
| Employees | Directory | |
|
|
|
| ERP Job Costs Summary | Budget | |
|
|
|
| Instructions | Instructions | |
|||
| Labor Productivity |
Budget OR timesheets |
|
|
|
|
| Labor Productivity: Budget | Budget | |
|
|
|
| Location | N/A | |
|
|
|
| Monitored Resource | Budget | |
|
|
|
| Owner Invoice | Prime contracts | |
|||
| Owner Invoice Line Item | Prime contracts | |
|||
| Prime Contract | Prime contracts | |
|||
| Prime Contract Change Order | Prime contracts | |
|||
| Prime Contract Change Order Line Item | Prime contracts | |
|||
| Prime Contract Change Order Markup | Prime contracts | |
|||
| Prime Contract Change Order Request | Prime contracts | |
|||
| Prime Contract Change Order Workflow Responses | Prime contracts | |
|||
| Prime Contract Change Order Workflow Steps | Prime contracts | |
|||
| Prime Contract Line Item | Prime contracts | |
|||
| Prime Contract Potential Change Order | Prime contracts | |
|||
| Prime Potential Change Order Production Quantity | Prime contracts | |
|
|
|
| Prime Workflow Responses | Prime contracts | |
|||
| Prime Workflow Steps | Prime contracts | |
|||
| Project | N/A | |
|
|
|
| Project Roles | N/A | |
|
|
|
| Request for Quote | Change events | |
|
|
|
| Request for Quote Quote | Change events | |
|
|
|
| Request for Quote Response | Change events | |
|
|
|
| RFI | RFI | |
|||
| RFI Assignee | RFI | |
|||
| RFI Question | RFI | |
|||
| RFI Response | RFI | |
|||
| Specifications | Specifications | |
|
|
|
| Sub Invoice Workflow Responses | Commitments | |
|||
| Sub Invoice Workflow Steps | Commitments | |
|||
| Subcontractor Invoice | Commitments | |
|||
| Subcontractor Invoice Line Item | Commitments | |
|||
| T&M Ticket | T&M Tickets | |
|
|
|
| T&M Ticket Equipment | T&M Tickets | |
|
|
|
| T&M Ticket Labor | T&M Tickets | |
|
|
|
| T&M Ticket Material | T&M Tickets | |
|
|
|
| Timecard Entry | Timesheets | |
|
|
T&M Tickets
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.
- Indicates that the task can be completed with the permission level.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Add a T&M Ticket to a Change Event 1 | |
|
||
| Add Equipment Entries on a T&M Ticket | |
|
||
| Best Practices for Configuring T&M Tickets | |
|||
| Create a T&M Ticket |
|
|
||
| Close or Reopen a T&M Ticket 2 | |
|
||
| Configure Advanced Settings: T&M Tickets | |
|||
| Create a Change Event from a T&M Ticket 1 | |
|
||
| Create Equipment from a T&M Ticket 2 |
|
|
||
| Delete a T&M Ticket 2 | |
|
||
| Edit a T&M Ticket 2 |
|
|
||
| Export a T&M Ticket as a PDF | |
|
|
|
| Request a Signature on a T&M Ticket |
|
|
||
| Retrieve a T&M Ticket 2 | |
|
||
| Search and Filter T&M Tickets |
|
|
|
|
| Sign a T&M Ticket |
|
|
|
|
| View a Change Event | To view a T&M ticket linked to a change event, you can use the Project Level Change Events tool. | |||
| View a T&M Ticket |
|
|
|
|
1 Users also need 'Standard' or 'Admin' level permissions on the project's Change Events tool.
2 Users with 'Standard' permission are only permitted to modify the tickets they create.
Transmittals
The following table highlights which user permissions are required to perform the described user action.
1 'Standard' users can only modify transmittals that they have created.
2 When a transmittal is marked 'Private', users with 'Read Only' or 'Standard' level permissions can see the transmittal only if one or more statements apply:
- They created the transmittal ('Standard' only).
- They are included in the 'To' or 'CC' fields on the transmittal.
- They have the 'View Private Transmittals Associated to Users within Same Company' granular permission enabled on their permissions template and another user in their company is the transmittal's creator or is included in the 'To' or 'CC' fields on the transmittal.