User Permissions Matrix - Web
- Last updated
- Save as PDF
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.
Tender 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.
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.
Directory (Company Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the tutorial.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Company level Directory tool?
Important
A user who is granted 'Admin' level permissions on the Company level Directory tool is automatically granted 'Admin' permissions across all Project level and Company level tools.Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Company to the Company Directory |
|
|
|||
Add a Distribution Group to the Company Directory |
|||||
Add a User Account to the Company Directory |
|
|
Users with granular permissions have the following limitations:
|
||
Add an Existing User to Projects in Your Company's Procore Account |
|
|
Users with granular permissions can only add other users to projects that they have already been added to. |
||
Add Insurance for a Vendor in the Company Directory |
|
|
|||
Allow Users to Create New Projects |
|||||
Assign a Company Permission Template to a User in the Company Directory |
|
|
Users with granular permissions have the following limitations:
|
||
Assign a Default Project Permissions Template to a User in the Company Directory |
|
|
Users with granular permissions can only assign users to assignable default project permissions templates. | ||
Assign a Project Permissions Template to a User in the Company Directory |
|
|
Users with granular permissions have the following limitations:
|
||
Change a User's Permissions to Company Tools in the Company Directory |
|
|
Users with granular permissions can only grant access to Company tools by assigning users to assignable company permissions templates. |
||
Change a User's Project Permissions Template in the Company Directory |
|
|
Users with granular permissions have the following limitations:
|
||
Configure Advanced Settings: Company Directory |
|||||
Customise the Column Display in the Directory Tool |
|||||
Deactivate a Company in the Company Directory |
|||||
Delete a Distribution Group from the Company Directory |
|||||
Designate an Insurance Manager for Your Procore Company |
|
|
|||
Download a vCard for a User Account in the Company Directory |
|||||
Download a Company or User Import Template |
|||||
Edit a Company in the Company Directory |
|
|
|||
Edit a Contact in the Company Directory |
|
|
|||
Edit a Distribution Group in the Company Directory |
|||||
Edit a User Account in the Company Directory |
|
|
Users with granular permissions have the following limitations:
|
||
Export the Company Directory to CSV or PDF |
|||||
Inactivate a Batch of Companies in the Company Directory |
|
|
|||
Inactivate a Batch of User Accounts in the Company Directory |
|
|
|||
Inactivate a Contact in the Company Directory |
|
|
|||
Inactivate a Company in the Company Directory |
|
|
|||
Invite a Batch of Procore Users to Join a Company's Procore Account |
|
|
|||
Invite or Re-invite a User to Procore |
|
|
|||
Merge Companies |
|||||
Reactivate a Batch of Companies in the Company Directory |
|
|
|||
Reactivate a Batch of User Accounts in the Company Directory |
|
|
|||
Reactivate a Contact in the Company Directory |
|
|
|||
Reactivate a Company in the Company Directory |
|
|
|||
Reactivate a User in the Company Directory |
|
|
|||
Refresh Tender Contacts for Connected Companies in the Company Directory |
|
|
|||
Remove an Existing User from Projects in Your Company's Procore Account |
|
|
Users with granular permissions can only remove other users from projects that they are a part of. | ||
Remove Company Insurance |
|
|
|||
Request Company and People Imports |
|||||
Respond to a 'Welcome to Procore' Email |
|||||
Search and Filter the Company Directory |
|||||
Send a Company or User Import Template to Procore |
|||||
Send a Procore Company to ERP Integrations for Accounting Acceptance |
|||||
Set Tenderer Information at the Company Level |
|
|
|||
Switch Between Views in the Company Directory |
|||||
Update Expiring Insurance for a Vendor in the Company Directory |
|
|
|||
View Company Details in the Company Level Directory Tool |
|
|
|||
View Merge Company History |
|||||
View User Details in the Company Level Directory Tool |
|
|
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)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the tutorial.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add Custom Response Sets to a Company Level Inspection Template |
|||||
Clone a Company Level Inspection Template |
|||||
Configure Advanced Settings: Company Level Inspections |
|||||
Create a Company Level Inspection Template |
|||||
Create a Custom Response Set for Inspections |
|||||
Delete a Company Level Inspection Template |
|||||
Delete an Inspection Type |
|||||
Edit a Company Level Inspection Template |
|||||
Edit a Custom Response Set for Inspections |
|||||
Search and Filter for Inspection Templates |
|||||
View the Change History of an Inspection Template |
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 Specific 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 |
---|---|---|---|---|
Check the Status of your Tender | 1 | |||
Configure Advanced Settings: Planroom | 1 | |||
Download Tender Documents | 1 | |||
Indicate your Intention to Tender | 1 | |||
Submit a Tender | 1 | |||
Submit a Pre-tender Question | 1 | |||
Update a Submitted Tender | 1 | |||
View a tender 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 place a tender on a project. Once a company is added to a tender package, tenderers within that company will automatically be given access to the Planroom upon logging into Procore.
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 This task requires 'Admin' level permissions on the Company level Directory tool OR 'Admin' level permissions on the Project level Admin tool for the project template. See Add an Existing User to Projects in Your Company's Procore Account.
3 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.
Programs
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add Programmes | * | |||
Add a Project to a Programme | * | |||
Assign a Project to a Different Programme | * | |||
Delete a Programme | * | |||
Edit Programme Information | * | |||
Remove a Project from a Programme | * | |||
View Programmes |
* 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.
Programme (Company Level)
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Create Calendar Items | ||||
Configure Advanced Settings: Company Level Programme | ||||
Search Project Programmes | ||||
View All Programme Tasks (for projects they have access to) | ||||
View All Programmed Tasks for All Projects |
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)
Learn which user permissions are required to take the described actions in this tool.
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the tutorial.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
Important
To see employees across all projects the following must be true:
- Users need 'Read Only' permissions or higher on the Company level Directory.
- Under Company Timesheets settings, the box must be marked for 'Can company employees be tracked on all projects?'.
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Customise the Column Display in the Company Level Timesheets Tool |
|||||
Delete a Timecard Entry in the Company Level Timesheets Tool |
Users with 'Standard' level permissions can only delete time entries that they have created. | ||||
Users with 'Standard' level permissions can only edit time entries that they have created. | |||||
Export Timecard Entries from Procore to Import into QuickBooks® Desktop |
|
||||
|
|||||
Export Timecard Entries from the Company Level Timesheets Tool |
|||||
|
|||||
Mark a Timecard Entry as Completed in the Company Level Timesheets Tool |
Additional permissions are required to complete this action:
|
||||
Perform Bulk Approval Actions in the Company Level Timesheets Tool |
|||||
Search and Filter Time Entries in the Company Level Timesheets Tool |
|||||
|
|||||
7 |
|
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
Admin (Project Level)
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
: Indicates that the task can only be completed when Procore is configured to use the Company level ERP Integrations tool. See ERP Integrations.
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.
Tendering
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
1 Users must also have 'Admin' level permission to the Project level Directory tool to complete this function.
Note: In projects updated to Tender 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 Tender 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 Tendering tool AND added to the Tendering CC Group can complete this function.
5 These tasks are performed by tenderers using the Company level Planroom tool. See Planroom.
Budget
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
: Indicates your company's Procore account must be configured to work with an integrated ERP system.
1 This task also requires 'Admin' permissions on the project's Client Contracts, Funding or Main 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.
4 Users also need 'Standard' or 'Admin' level permissions on the Commitments tool.
5 Collaborators can submit a quote only if they receive an RFQ email notification. To be eligible to receive an email, the collaborator's user account must be granted 'Standard' level permissions on the project's Commitments tool and designated as the 'Assignee' on the RFQ. For details, see Assign and Send an RFQ to a Collaborator and Submit a Quote as a Collaborator.
Variations
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 Variations tool, you must be the 'Designated Reviewer' on the variation. See Create a Commitment Variation.
2 Users with 'Admin' level permissions on the project's Variations tool must be granted additional tool permissions: (1) To edit a Commitment Variation (CV), 'Admin' level permissions on the project's Commitments tool, and/or (2) to edit a Main Contract Variation (MCV), 'Admin' level permissions on the project's Main Contracts tool. Additional factors may also apply. For details, see Edit a Variation.
3 Users with 'Read Only' or 'Standard' level permissions on the project's Variations tool can view variations 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 Variations tool can also view variations 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 Main 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 Variations Tool |
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 one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
: Indicates your company's Procore account must be configured to work with an integrated ERP system.
1 To perform this task, downstream collaborators should be designated as a payment application contact on the commitment. See Add Payment application Contacts to a Commitment.
2 Also requires a DocuSign© account.
3 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 a Payment Application Contact. See Add Payment application Contacts to a Purchase Order or Subcontract.
4 Commitments synced with an integrated ERP system cannot be deleted until they are unlinked. See Delete a Commitment Synced with QuickBooks® Desktop and Delete a Commitment Synced with Sage 300 CRE®.
5 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 to the PDF file format if they have been granted access to the purchase order or subcontract via the Private drop-down list and the 'Allow These Users to See BOQ Items' tickbox is enabled.
6 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.
7 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.
8 Also requires 'Standard' or 'Admin' permission on the project's Change Events tool.
9 Users with 'Standard' level permissions on the project's Commitments tool can create PVs when they are added to the 'Private' drop-down list and the 'Allow Standard Level Users to Create PVs' configuration must be selected.
10 The payment application must be in the 'Draft' or 'Revise and Resubmit' status for a user with 'Standard' level permissions to delete it.
Co-ordination 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.
Correspondence
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 one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
1 Users with 'Read Only' level permissions and the necessary granular permissions on a correspondence type can perform this task for correspondence items that they created.
2 Users with 'Standard' level permissions on a correspondence type can perform this task for correspondence items that they created.
3 Users will need additional permissions depending on the new item's tool.
4 Users will need additional permissions on the project's Drawings 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.
Site Diary
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the project's Site Diary tool?
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Photo to a Site Diary Entry so that it Populates in the Photos Tool |
|
||||
Add a Related Item to a Site Diary Entry |
|||||
Approve Any Site Diary Entry Created by Collaborators |
|||||
Approve Copied Site Diary Entries Created by Collaborators |
|||||
Configure Advanced Settings: Site Diary |
|||||
Copy a Site Diary |
On an iOS device, this action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create a Site Diary Entry from the Calendar View | |||||
Create Accident Diary Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Call Diary Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Daily Construction Report Diary Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Daily Construction Report Diary Entries as a Collaborator |
|
|
|
||
Create Site Diary Entries as a Collaborator |
|
|
The granular permission for 'Collaborator Entry Only' has to be on a global template before the option is available in the Site Diary configuration settings. |
||
Create Delay Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Delivery Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Delivery Entries as a Collaborator |
|
|
|
||
Create Dumpster Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Equipment Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Inspection Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Manpower Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Manpower Entries as a Collaborator |
|
|
|
||
Create Note Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||||
Create Note Entries as a Collaborator |
|
|
|
||
Create Observed Weather Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Plan Revision Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Productivity Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Quantity Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Safety Violation Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Programmed Work Entries |
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||||
Create Timecard Entries for Any User |
|
||||
Create Timecard Entries for Yourself |
Users with 'Standard' level permissions must also be marked as an employee of your company. |
||||
Create Visitor Entries |
|||||
Create Pending Visitor Entries as a Collaborator |
|
|
The granular permission for 'Collaborator Entry Only' has to be on a global template before the option is available in the Site Diary configuration settings. | ||
Create Waste Entries |
|||||
Create a Change Event from a Site Diary Entry |
|||||
Create a Custom Report from the Site Diary |
|||||
Delete Any Site Diary Item |
Entries cannot be deleted on a day that has been marked as complete. If an entry needs to be deleted, an 'Admin' user can Re-Open a Site Diary. | ||||
Delete a Site Diary Item You Created |
|
|
Entries cannot be deleted on a day that has been marked as complete. If an entry needs to be deleted, an 'Admin' user can Re-Open a Site Diary. |
||
Delete a Site Diary Item You Created as a Collaborator |
|
|
Entries cannot be deleted after they are approved by a Site Diary Admin.
|
||
Delete Related Items from Site Diary Entries |
|||||
Edit Any Site Diary Item |
On an Android device, this action can be performed offline, provided that the item was previously viewed and cached on your mobile device. | ||||
Edit a Site Diary Item You Created |
|
||||
Edit a Site Diary Item You Created as a Collaborator |
|
|
Entries cannot be edited after they are approved by a Site Diary Admin. |
||
Email a Site Diary |
|||||
Enter Logs for a Previous Day |
|
This action can also be performed on mobile. | |||
Export a Site Diary as PDF |
|||||
Mark a Site Diary as Complete |
|||||
Reopen a Site Diary |
|||||
Resubmit a Site Diary Entry as a Collaborator |
|
|
|||
Search and Filter Site Diaries |
|||||
Search and Filter Site Diary Entries You Created as a Collaborator |
|
|
|||
Upload Photos to the Site Diary |
|||||
Upload Photos to the Site Diary from the Photos Tool |
Users also need 'Standard' permissions or higher on the project's Photos tool. | ||||
View and Attach Files to a Site Diary |
On an Android device, this action can be performed offline, provided that the item was previously viewed and cached on your mobile device. | ||||
View Any Site Diary Items |
|
||||
View Your Site Diary Items as a Collaborator |
|
|
The granular permission for 'Collaborator Entry Only' has to be on a global template before the option is available in the Site Diary configuration settings. | ||
View Site Diary Items by Users at your Company as a Collaborator |
|
|
The granular permission for 'Collaborator Entry Only' has to be on a global template before the option is available in the Site Diary configuration settings. | ||
View Change History Log |
|||||
View Site Diary Notes Report |
Users also need 'Read Only' level permissions or higher on the project's Reports tool. |
||||
View Site Diaries in the Calendar View |
Direct Costs
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Directory (Project Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Directory tool?
Important
A user who is granted 'Admin' level permissions to the Project level Directory tool is also automatically granted 'Admin' permissions to all of the project's tools.Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Company to the Project Directory |
|
|
On a mobile device, this action can be performed offline. Tasks performed offline are be synced with Procore when a network connection is reestablished. | ||
Add a Distribution Group to the Project Directory |
|
|
|||
Add a Contact to your Device |
On a mobile device, this action can be performed offline. | ||||
Add a Phone Calls Entry from the Directory |
|||||
Add a User Account to the Project Directory |
|
|
On a mobile device, this action can be performed offline. Tasks performed offline are be synced with Procore when a network connection is reestablished. | ||
Add Project Insurance to a Company Record in the Project Directory |
|||||
Assign a Project Permissions Template to a User in the Project Directory |
|
|
Users with granular permissions have the following limitations:
|
||
Bulk Add Users and Companies to a Project Directory |
|
|
Users with the granular permission can only assign 'Assignable Permission Templates' to others based on their own permissions template settings. | ||
Change a User's Permissions in the Project Directory |
|
|
Users with the granular permission can only assign 'Assignable Permission Templates' to others based on their own permissions template settings. | ||
Configure the Project Team on the Project Home Page |
|
|
|||
Configure Advanced Settings for the Project Directory |
|||||
Create a Project Specific Permissions Template from the Project Directory |
|||||
Customise the Column Display in the Directory Tool |
|||||
Delete a Distribution Group from the Project Directory |
|||||
Download vCard for a User Account in the Project Directory |
|||||
Edit a Company in the Project Directory |
|
|
|||
Edit a Distribution Group |
|
|
|||
Edit an Active Account in the Project Directory |
|
|
Only users with 'Admin' level permissions can edit inactive user accounts. | ||
Edit an Inactive Account in the Project Directory |
|||||
Email Forward Contact Information |
|||||
Enable Programme Notifications for a User on a Project |
|||||
Enable Weather Delay Alerts by Phone or Email |
|||||
Export the Project Directory to CSV or PDF |
|||||
Forward Contact Information by Email |
|||||
Invite or Reinvite a User to Join a Procore Project |
|
|
|||
Invite a Batch of Users to Join a Procore Project |
|
|
|||
Reactivate a Company in the Project Directory |
|||||
Reactivate a User in the Project Directory |
|||||
Remove a Company from the Project Directory |
|
|
|||
Remove a User from a Project |
|
|
|||
Remove Project Insurance from a Company Record |
|||||
Remove a Batch of User Accounts from a Project Directory |
|
|
|||
Remove a Batch of Companies from a Project Directory |
|
|
|||
Request Company and People Imports |
|
||||
Save Contact to Phone on a Mobile Device |
|||||
Search and Filter the Project Directory |
|||||
Send a Message or WhatsApp to a Contact |
|||||
Set Tenderer Information at the Project Level |
|||||
Switch Between Views in the Project Directory |
|||||
View the Project Directory |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
Documents (Project Level)
Learn which user permissions are required to take the described actions in this tool.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Documents tool?
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Related Item to a File |
|||||
Add or Edit a File Description |
|||||
Change Permission Settings on a Folder or File |
|
|
|||
Check In or Out a File |
|||||
Configure Advanced Settings: Documents |
|||||
Create a Folder |
|||||
Delete Files or Folders |
|
|
|||
Download a Previous Version of a File |
|||||
Download Files and Folders |
|||||
Email Files and Folders |
|
||||
Export Information |
|||||
Export Object Data from a Model |
Users must also have 'Read Only' or higher permission to the Models tool. | ||||
Manage and Set Tags for Documents |
|||||
Manage Permissions for Files and Folders |
|
|
|||
Manage Who Tracks Files and Folders |
|||||
Move and Copy Files and Folders |
|
|
|
||
Open or Edit a File in Microsoft Office 365 |
|||||
Preview a File |
|||||
Rename a File |
|
|
|||
Rename a Folder |
|
|
|||
Retrieve a File or Folder from the Recycle Bin |
|||||
Search for and Filter Documents |
This action can be performed offline provided that the asset/item was previously viewed and cached on your mobile device. | ||||
Sort Document Folder Contents |
|||||
Track a Folder or File |
|||||
Upload a New Version of a File |
|||||
Upload Files into a Folder |
This action can be performed offline. Actions performed offline will be synced with Procore once a network connection has been reestablished. | ||||
View a File in Microsoft Office 365 |
|||||
View Documents |
|||||
View a Private File or Folder |
|
|
The user must have the 'Access Private Folders and Files' granular permission OR must be added to the permissions list for the file or folder. See Manage Permissions for Files and Folders. |
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 one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
1 Users must also have 'Read Only' or higher permissions on the project's Photos tool.
2 Users with 'Standard' level permissions on the Drawings tool can delete published drawing markups if the 'Allow Standard level users to delete published markup' setting is enabled for the project. See Allow Users To Delete Published Markups.
3 Only users with 'Admin' permissions can subscribe or unsubscribe other users to the Drawings tool.
4 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.
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 Tender | ||||
Generate Tender Estimates | ||||
Manage Takeoffs | ||||
Set the Drawing Scale for Takeoffs | ||||
View an Estimate | ||||
View the Tender | ||||
View Takeoffs |
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.
2 'Standard' users can edit forms 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.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Project Photo to the Home Page | This is set in the Project level Photos Tool. | |||
Add Favourites to the Project Tools Menu | ||||
Add, Modify and Remove Project Home Links | ||||
Add the Project Team to the Project Home Page | ||||
Change the Project Address | This is updated in the Project level Admin Tool. | |||
Change Your Login ID Email Address for Your Procore User Account | ||||
Configure Advanced Settings: Project Home | ||||
Edit My Account Settings | ||||
Open Items from the Project Overview in the Project's Home page | ||||
Rearrange Your Project Level Navigation Bar | ||||
Set Up a Persistent Project Message for the Home Page | ||||
Show or Hide Project Weather on the Project Home Page | ||||
View the Home Page | ||||
View Project Weather on the Home Page | ||||
View Recently Changed Items on a Project |
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.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Related Item to an Incident | ||||
Add an Environmental Record to an Incident | 1 | |||
Add an Injury/Illness Record to an Incident | 1 | |||
Add a Near Miss Record to an Incident | 1 | |||
Add a Property Damage Record to an Incident | 1 | |||
Close an Incident | 1 | |||
Configure Advanced Settings: Incidents | ||||
Create an Incident | ||||
Delete an Incident | ||||
Delete an Incident Record | ||||
Edit a Near Miss Record | 1 | |||
Edit an Incident | 1 | |||
Edit an Injury/Illness Record | 1 | |||
Email Incidents | 2 | |||
Export Incidents as a PDF or CSV | ||||
Retrieve an Incident From the Recycle Bin | ||||
View an Incident |
1 'Standard' users can edit assets in incidents that they create.
2 'Standard' users can only email incidents that they create.
Inspections (Project Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Inspections tool?
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Related Item to an Inspection |
|
||||
Add Comments to an Inspection Item |
|
||||
Add Company Level Inspection Templates to Your Project |
|
||||
Add Attachments to Inspection Items |
|
||||
Add Signers to an Inspection |
On an iOS mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. | ||||
Close an Inspection You Created |
|||||
Close Any Inspection |
|||||
Configure Advanced Settings: Inspections |
|||||
Create an Inspection |
On a mobile device, this action can be performed offline. Tasks performed offline are synced with Procore when a network connection is reestablished. | ||||
Create a Project Level Inspection Template |
|||||
Create an Observation from an Inspection |
|
||||
Delete an Inspection |
|||||
Create an Inspection Programme |
|
||||
Delete an Inspection Template |
|||||
Edit an Inspection |
|
||||
Edit a Project Level Inspection Template |
|||||
Edit an Inspection Schedule |
|
||||
Email Inspections |
|||||
Export an Individual Inspection |
|||||
Perform an Inspection |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. | ||||
Retrieve an Inspection From the Recycle Bin |
|||||
Search and Filter for Inspections |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
||||
Sign an Inspection |
On an iOS mobile device, this action can be performed offline. Tasks performed offline are synced with Procore when a network connection is reestablished. | ||||
View Project Level Inspections |
|||||
View the Activity Feed of Items in an Inspection |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
||||
View Change History of an Inspection |
|||||
View Signatures on an Inspection |
On an iOS mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
Instructions
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Related Item to an Instruction | ||||
Add the Instructions Tool to a Project | 1 | |||
Configure Advanced Settings: Instructions | ||||
Create an Instruction from an RFI | 2 | |||
Create and Issue an Instruction | ||||
Edit and Re-Issue an Instruction | 3 | |||
Email an Instruction | ||||
Export an Instruction | ||||
Export the Instructions List | ||||
Delete an Instruction | ||||
Retrieve an Instruction from the Recycle Bin | ||||
Set User Permission for the Instructions Tool | ||||
Switch Between Views in the Instructions Tool |
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.
Payment applications
User access to the Project level Payment applications tool depends on the user's access permission to the contracts in the Project level Main Contracts and/or Commitments tool. The tables below highlight which permissions are required for each tool in order to perform specific tasks with the Payment applications tool.
Payment Applications
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Bulk Edit Subcontractor Payment application Status with the Payment Applications Tool | 1 | |||
Bulk Send Subcontractor Payment applications to DocuSign® with the Payment Applications Tool | 1 | |||
Compile Subcontractor Payment application Backups with the Payment Applications Tool | 1 | |||
Configure Settings: Payment Applications | 1 | |||
Create Automatic Billing Periods | 1 | |||
Create Manual Billing Periods | 1 | |||
Create a Subcontractor Bill of Quantities (SBOQ) | 2 | 2 | 1 | |
Edit Billing Periods | 1 | |||
Manage Billing Periods | 1 | |||
Update a Subcontractor Bill of Quantities as a Payment Application Contact from the Payment Applications Tool | 2 | 2 |
1 To perform this task from the project's Payment applications tool, you must be an payment application administrator.
2 To perform this task, you must have the permissions designated in the tutorial and you must be an payment application contact. By default, payment application contacts are added to the 'Private' list of a commitment.
Main Contracts
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Create a Main Contract Payment Applications | ||||
Create a Record for a Payment Received | ||||
Delete Main Contract Payment Applications | ||||
Edit Main Contract Payment Applications | ||||
Email Main Contract Payment Applications | ||||
Export Main Contract Payment Applications | ||||
View a Summary Preview of an Owner Payment application |
Commitments
The following table highlights which user permissions are required to perform the described user action with the Payment Applications tool.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Accept or Decline an 'Invite to Bill' as a Payment Application Contact | 4 | |||
Add a New Payment to the Payments Issued Tab of a Commitment | ||||
Add Payment application Contacts to a Purchase Order or Subcontract (Legacy) | ||||
Add Payment application Contacts to a Purchase Order or Subcontract | ||||
Add a Subcontractor BOQ to a Commitment | ||||
Create a Payment Issued | ||||
Create a Payment Application on Behalf of a Payment Application Contact | 1 | |||
Create a New Subcontractor Payment application as a Payment Application Contact | 1 | |||
Create a Subcontractor Payment application for Release of Retention | 3 | |||
Create a Payment Received for a Main Contract | ||||
Delete a Subcontractor Payment application | 6 | |||
Enable or Disable a Subcontractor BOQ Tab on a Commitment | ||||
Enable the Payments Issued Tab on a Commitment | ||||
Forward a Subcontractor Payment application by Email | 2 | |||
Review a Subcontractor Payment application as a Payment Application Administrator | ||||
Review Payment Application Line Items as a Payment Application Contact | 2 | |||
Revise & Resubmit a Subcontractor Payment application as a Payment Application Contact | 4 | |||
Send an 'Invite to Bill' to a Payment Application Contact | ||||
Set or Release Retention on a Subcontractor Payment Application | 3 | |||
Submit a New Payment application as a Payment Application Contact | 1 | 1 | ||
Update a Subcontractor Bill of Quantities as a Payment Application Contact from the Payment Applications Tool | 5 | 5 |
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 Payment application Contact on the commitment. See What is a payment application contact?
2 To perform this task, downstream collaborators should be designated as a payment application contact on the commitment. See What is a payment application contact?
3 To perform this task and to release retention during the current billing period, users must have 'Standard' permission on the project's Commitments tool or be designated as a payment application contact on the commitment. See What is a payment application contact? To set retention, 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 a payment application 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 a payment application contact on the purchase order or subcontract. 'Read Only' users must be added to the 'Private' list.
6 The payment application must be in the 'Draft' or 'Revise and Resubmit' status for a user with 'Standard' level permissions to delete it.
Meetings
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Meetings tool?
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Comment to a Meeting Item |
|
||||
Add a Meeting Category |
|
|
|||
Add a Meeting Item |
|
|
|||
Add a Meeting To Your Personal Calendar |
|||||
Add a Related Item to a Meeting |
|
|
|||
Add Meeting Minutes |
|||||
Configure Advanced Settings: Meetings |
|||||
Convert a Meeting from Agenda to Minutes Mode |
|
|
|||
Create a Follow-up Meeting |
|||||
Create a Meeting |
|
|
|||
Delete Any Meeting Comment |
|||||
Delete Own Meeting Comment |
|
||||
Create a Meeting from a Template |
|
|
|||
Delete a Meeting |
|||||
Delete a Meeting Category |
|
|
|||
Delete a Meeting Item |
|
|
|||
Distribute a Meeting Agenda |
|
|
|||
Distribute and Redistribute Meeting Minutes |
|
|
|||
Edit a Meeting |
|
|
|||
Edit a Meeting Item |
|
|
|||
Export a Meeting as a PDF |
|||||
Forward a Meeting by Email |
|
|
|||
Initiate an Email Communication Thread for a Meeting |
Any person (even non-Procore users) with the email address for the meeting can initiate a communication thread. | ||||
Record Meeting Attendance |
|||||
Reorder Meeting Categories |
|
|
|||
Reorder Meeting Items |
|
|
|||
Search for a Meeting |
|||||
Star Previous Minutes |
|||||
View a Meeting |
|||||
View Previous Minutes |
|||||
View the Change History of a Meeting |
Models
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard 1 | Admin |
---|---|---|---|---|
Add a Section Box to a Model | 3 | |||
Associate a Model with a Procore Project | ||||
Create a Co-ordination Issue in the Model Viewer | 2 | |||
Delete a Model | ||||
Download the Procore Plugin for the Models Tool | ||||
Edit Information for a Model | ||||
Edit a Co-ordination Issue in the Model Viewer | 2 | |||
Publish a Model to Procore | 3 | |||
Publish a New Version of a Model | 3 | |||
Reassociate a Model with a Procore Project | ||||
Search for and Filter Co-ordination Issues in the Model Viewer | 2 | |||
Search for and Sort Models | ||||
Use the Section Tool on a Model | ||||
View a Model | ||||
View the Version History of a Model |
1 'Standard' level permission does not exist for the Models tool.
2 Users also need 'Standard' or 'Admin' level permissions to the Coordination Issues tool.
3 Users also need 'Read Only' or higher level 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.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Comment to an Observation | ||||
Add a Related Item to an Observation | ||||
Add Project Level Observation Types | 1 | |||
Bulk Edit Observations | ||||
Bulk Delete Observations | ||||
Bulk Retrieve Observations | ||||
Respond to an Observation | +2 | |||
Close an Observation | +2 | |||
Configure Advanced Settings: Observations | ||||
Customise the Column Display in the Observations Tool | ||||
Create an Observation | 3 | |||
Create an Observation from an Inspection | 7 | |||
Delete an Observation | ||||
Delete Project Level Observation Types | 1 | |||
Edit Project Level Observation Types | 1 | |||
Edit an Observation | 4 | |||
Email Observations | ||||
Export Observations as a PDF or CSV | ||||
Can Be Included on the Distribution List | ||||
Reject an Observation | ||||
Respond to an Observation | 2 | |||
Retrieve an Observation from the Recycle Bin | ||||
Search for and Filter Observations | ||||
Update the Status of an Observation | +8 | +8 | ||
View the Activity Stream of an Observation | ||||
View Observations | 5 | +6 | ||
View Observations by Type |
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.
8 'Read Only' and 'Standard' users with the granular permission to 'Update Status and Comment on Observations Assigned to Users within Same Company' can only update the status to 'Ready for Review'.
Photos
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 application.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Comment to a Photo | ||||
Add a Description to a Photo | ||||
Bulk Edit Photos | 1 | |||
Configure Advanced Settings: Photos | ||||
Create a Photo Album | + | |||
Delete a Photo Album | + | + | ||
Delete Photos | ||||
Download Photos | ||||
Email Photos (Inbound) | ||||
Email Photos (Outbound) | ||||
Export a Photo as a PDF | ||||
Find Starred (Favorited) Photos | ||||
Mark a Photo as Private | ||||
Mark an Album as Private | ||||
Move Photos | ||||
Rename an Album | ||||
Reorder a Photo Album | + | + | ||
Retrieve a Photo from the Recycle Bin | ||||
Rotate Photos | ||||
Search and Filter Photos | ||||
Set a Project Photo | ||||
Set Photo Location | ||||
Star a Photo | ||||
Subscribe to Photos | ||||
Upload Photos | ||||
View Photos | ||||
View Private Photos | + | + |
1 Users with 'Standard' level permissions on the project's Photos tool may only bulk edit photo descriptions.
Main Contracts
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add Financial Markup to Main Contract Variations | ||||
Add a Related Item to a Main Contract Variation | ||||
Approve a Main Contract | ||||
Configure Advanced Settings: Main Contract | ||||
Create Variation Request | ||||
Create Payment Received for a Main Contract | ||||
Create Main Contract Payment Applications | ||||
Create a Main Contract | + | + | ||
Create a Potential Variation for a Main Contract 1 | ||||
Create a Main Contract Variation | ||||
Create Bill of Quantities (BOQ) from the Budget | ||||
Delete a Main Contract | + | + | ||
Edit a Commitment Variation Linked to a Potential Variation for a Main Contract | ||||
Edit a Main Contract 2 | + | + | ||
Edit the Advanced Settings on a Main Contract | ||||
Email Main Contract Payment Applications | ||||
Email a Potential Variation for a Main Contract | ||||
Email Main Contract | ||||
Enable Financial Markup on a Main Contract | ||||
Export Main Contract Payment Applications | ||||
Export a Main Contract 3 | ||||
Filter Main Contract Variations | ||||
Import a Main Contract CSV | ||||
Remove a Variation from a Main Contract | ||||
Delete a Main Contract Variation | ||||
Search for and Add Filters to Main Contracts | ||||
Set Up a Main Contract | ||||
View Main Contract 2 | ||||
View the Change History of a Main Contract |
1 Users with 'Standard' level permissions can only create a PV if the 'Allow Standard Level Users to Create PVs' tickbox is enabled in the Configure Settings page. For more information, see Configure Advanced Settings: Main Contract.
2 Users with 'Read Only' and 'Standard' level permissions can only view a main contract that is private if they have been added to the 'Private' drop-down list on the main contract.
3 Users with 'Read Only' or 'Standard' level permissions can only export to the PDF file format. Users with 'Admin' level permissions can export to both DOCX and PDF.
Snag List
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.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add Attachments to a Snag List Item | ||||
Add Comments to Snag List Items | ||||
Assign a Snag List Item to a 'Standard' or 'Admin' Level User | ||||
Assign a Snag List Item to an 'Admin' level User Only | ||||
Close Snag List Item 3 | ||||
Configure Advanced Settings: Snag List | ||||
Customise the Column Display in the Snag List Tool | ||||
Create a Project Level Snag Item Template | ||||
Create a Snag List Item 2 | ||||
Create a Snag Item Template Category at the Project Level | ||||
Deactivate a Snag Item Template on a Project | ||||
Delete a Snag Item Template Category at the Project Level | ||||
Delete a Snag Item Template from a Project | ||||
Delete a Snag List Item | ||||
Edit a Snag List Item 6 | ||||
Edit a Snag Item Template Category at the Project Level | ||||
Export Snag List Log as a PDF | ||||
Export the Snag List Log as a CSV | ||||
Export the Snag List Log as a PDF | ||||
Import Snag List Items 7 | ||||
Respond to a Snag List Item 4, 1 | + | + | ||
Retrieve Deleted Snag Item from Recycle Bin | ||||
Search and Filter the Snag List | ||||
Notify Assignees of Snag List Items | ||||
View a Snag List Item 5 | ||||
View Change History of a Single Snag List Item | ||||
View Private Snag Items Assigned to User Within the Same Company | + | + |
1 Users with 'Standard' level permissions can perform this action if they are listed as the item's Snag Item Manager, Assignee or Final Approver or if they have been granted the granular permission "Respond to Snag Items Assigned to Users within the Same Company."
2 'Standard' level users can only list 'Admin' level users as the 'Assignee' on a snag list item. However, 'Standard' level users who have been granted permission to act as a Snag Item Manager can list other 'Standard' level users as the 'Assignee' on a snag list item.
3 'Standard' level users can only close snag list items they have created (when the item's status is 'Draft' or 'In Dispute'), or when they have been designated as the item's 'Final Approver' (when the item's status is 'Ready to Close') or designated as the item's 'Snag Item Manager'.
4 Users with 'Read Only' permissions can perform this action if they have been granted the granular permission “Respond to Snag Items Assigned to Users within the Same Company.”
5 Users with 'Standard' and 'Read Only' permissions can only view non-private snag list items after they have been sent to the Assignee.
6 Users with 'Standard' permissions can only perform this action for items they created.
7 This task also requires 'Admin' permissions on the project's Admin tool and 'Standard' permissions on the project's Directory 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 Snag List Delays | 3 | 3 | 3 | |
View Vendor Insurance Report | 4 | 4 | 4 | |
View Watch Folders Report | 3 | 3 | 3 | |
View Labour 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 Main Contract Variations | ||||
View Committed Cost Report | ||||
View Overdue Commitment Variations | ||||
View Subcontractor Payment Applications by Date | ||||
View Unexecuted Main Contract Variations | ||||
View Main Potential Variation Report By Change Reason | ||||
View Monitored Resources Report | 5 | 5 | 5 |
Programme Reports | None | Read Only | Standard | Admin |
---|---|---|---|---|
View All Programme Reports |
Site Diary Reports | None | Read Only | Standard | Admin |
---|---|---|---|---|
View All Site Diary 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 Variation | Commitments | ||||
Commitment Variation Line Item | Commitments | ||||
Commitment Variation Markup | Commitments | ||||
Commitment Variation Request | Commitments | ||||
Commitment Variation workflow Responses | Commitments | ||||
Commitment Variation workflow steps | Commitments | ||||
Commitment Line Item | Commitments | ||||
Commitment Potential Variation | 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 | ||||
Labour Productivity |
Budget OR timesheets |
||||
Labour Productivity: Budget | Budget | ||||
Location | N/A | ||||
Monitored Resource | Budget | ||||
Owner Payment application | Main contracts | ||||
Owner Payment application Line Item | Main contracts | ||||
Main Contract | Main contracts | ||||
Main Contract Variation | Main contracts | ||||
Main Contract Variation Line Item | Main contracts | ||||
Main Contract Variation Markup | Main contracts | ||||
Main Contract Variation Request | Main contracts | ||||
Main Contract Variation Workflow Responses | Main contracts | ||||
Main Contract Variation Workflow Steps | Main contracts | ||||
Main Contract Line Item | Main contracts | ||||
Main Contract Potential Variation | Main contracts | ||||
Main Potential Variation Production Quantity | Main contracts | ||||
Main Workflow Responses | Main contracts | ||||
Main Workflow Steps | Main 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 Payment application Workflow Responses | Commitments | ||||
Sub Payment application Workflow Steps | Commitments | ||||
Subcontractor Payment application | Commitments | ||||
Subcontractor Payment application Line Item | Commitments | ||||
Daywork Sheet | Daywork Sheets | ||||
Daywork Sheet Equipment | Daywork Sheets | ||||
Daywork Sheet Labour | Daywork Sheets | ||||
Daywork Sheet Material | Daywork Sheets | ||||
Timecard Entry | Timesheets |
RFIs
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 one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Related Item to an RFI | ||||
Add Assignees to an RFI as an Assignee on an RFI | 1 | 1 | ||
Choose an "Official Response" for an RFI | + 2 | + 2 | ||
Close an RFI | + 2 | + 2 | ||
Configure Settings: RFIs | ||||
Create a Potential Variation from an RFI | 3 | |||
Create an Instruction from an RFI | 4 | 4 | 4 | |
Create an RFI | + 5 | |||
Create and View a Custom RFI Report | ||||
Customise the Column Display in the RFIs Tool | ||||
Delete a Response to an RFI | ||||
Delete an RFI | ||||
Designate the Default RFI Manager for a Project's RFIs | ||||
Edit a Custom RFI Report | 6 | |||
Export an RFI | ||||
Export the RFIs List to CSV or PDF | ||||
Edit an RFI | + 2 | + 2, 5 | ||
Forward an RFI by Email | ||||
Forward an RFI for Review | 7 | 7 | ||
Perform Bulk Actions on RFIs | ||||
Reopen an RFI | + 2 | + 2 | ||
Respond to an RFI | + 2 | + 2, 8 | ||
Resize the Column Width in the RFIs Log | ||||
Retrieve an RFI from the Recycle Bin | ||||
Search for and Filter RFIs | ||||
Share a Custom RFI Report | ||||
Shift the Action required by on a RFI | + 2 | + 2 | ||
View RFIs | 9 | 9 | ||
View the Distribution History of a Custom RFI Report |
1 The user adding to the RFI's 'Assignee' list must first be designated as an 'Assignee' and must be the current Ball In Court person.
2 Users with 'Read Only' or 'Standard' level permissions on the project's RFIs tool with the 'Act as RFI Manager' granular permission enabled on their permissions template can perform this task for RFIs that they create ('Standard' only) or that they are designated as RFI Manager for. For more information about what tasks users with this granular permission enabled on their permissions template can perform, see What tasks does the RFI Manager granular permission allow users to perform?
3 To create a Potential Variation from an RFI, you must first complete the steps in Create an RFI, the main contract must be in the 'Approved' status, the Change Events tool must be disabled on the project and the Main Contracts tool must be configured for two (2) or three (3) tier variations. If the Change Events tool is enabled, follow the steps in Create a Change Event from an RFI instead.
4 Users with 'Read Only' or 'Standard' level permissions on the RFIs tool AND 'Standard' level permissions or higher on the Instructions tool can create instructions from RFIs that they have access to.
5 Users with 'Standard' level permission without the 'Act as RFI Manager' granular permission enabled on their permissions template can only create or edit their RFIs in the 'Draft' status.
6 Users with 'Standard' level permission can only edit the custom reports that they create.
7 Users must be designated as an Assignee for the RFI and be the current Ball In Court person to forward the RFI for review.
8 Users with 'Standard' level permission can reply to RFIs if they have been added as members of the RFI's distribution list.
9 Users may require specific roles on an RFI (or granular permissions) to view the RFI depending on the RFI's status and privacy settings. See View RFIs for details.
Programme (Project Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Programme tool?
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add Related Items to a Programmed Task |
|||||
Configure Advanced Settings: Programme |
|||||
Configure Programme Notification Emails |
|||||
Configure the Project Level Programme Tool for Primavera P6 |
|||||
Clear an Integrated Programme |
|||||
Create a Calendar Item |
|||||
Create Lookahead |
|
|
|||
Create Lookahead Tasks |
|
|
|||
Delete Calendar Item |
|||||
Delete Lookahead |
|
|
|||
Delete Lookahead Tasks |
|
|
|||
Edit Any Calendar Item |
|||||
Edit a Calendar Item You Created |
|||||
Edit Lookahead Task |
|
|
|||
Export a Project Programme |
|||||
Request a Programme Change |
|||||
Search and Filter for Programmed Tasks |
|||||
Send Recurring Project and Resource Programmes |
|||||
Update a Project Programme File |
|||||
Update Lookahead Tasks |
|
|
|||
Update Task Completion Percentage |
|
|
|||
Upload a Project Programme File to Procore's Web Application |
|||||
Upload an Asta Powerproject Programme |
|||||
View a Project Programme |
|||||
View a Programmed Task |
|||||
View Lookaheads |
|||||
View the Change History of Lookaheads |
|
|
Specifications
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 Related Item to a Specification | ||||
Configure Advanced Settings: Specifications | ||||
Create a Specification Set | ||||
Delete Pending Specification Uploads | ||||
Delete Spec Section Revisions | ||||
Download Specifications | ||||
Edit Spec Sections and Divisions | ||||
Email Specifications | ||||
Export Specifications as a PDF or CSV | ||||
Manage Specification Log | ||||
Manually Create Divisions | ||||
Manually Create Spec Sections | ||||
Mark Specifications as Obsolete | ||||
Open Specifications | ||||
Review and Publish Specifications | ||||
Search and Filter for Specifications | ||||
Search Contextually Within Specifications | ||||
Submittal Builder: Add Submittals | 1 | 1 | 1 | |
Submittal Builder: Configure Submittal Titles | 1 | 1 | 1 | |
Upload Specification Revisions | ||||
Upload Specifications | ||||
View a Deleted Specifications Report | ||||
View Report of All Specification Revisions | | |||
View Specifications | ||||
View Specification Change History | ||||
View Specification Download Log | ||||
View Specification Related Items |
1 Also requires 'Admin' level permission on the Project level Submittals tool.
Submittals
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 one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Related Item to a Submittal | ||||
Add a Related Item to a Submittal Package | ||||
Add a Submitter and Approvers to the Submittal Workflow | ||||
Add an Existing Submittal to a Submittal Package | ||||
Apply a Submittal Workflow Template to a Submittal | ||||
Bulk Edit Submittals in a Package | ||||
Change the Action Required By on a Submittal | ||||
Close a Submittal | ||||
Configure Advanced Settings: Submittals Tool | ||||
Create Custom Submittal Log Statuses | ||||
Create Custom Submittal Responses | ||||
Create Custom Submittal Types | Configure this setting in the Admin Tool (Company Level) | |||
Create a Bluebeam Studio Session | 1 | |||
Create a Custom Submittals Report | 2, 4 | 3, 4 | ||
Create a New Submittal in a Submittal Package | ||||
Create a Submittal | + | + | ||
Create a Submittal Package | + | + | ||
Create a Submittal Revision | +5 | +5 | ||
Customise the Column Display in the Submittals Tool | ||||
Delete a Custom Submittal Report | ||||
Delete a Submittal | ||||
Delete a Submittal Package | ||||
Designate the 'Default Submittal Manager' for the Submittals Tool | ||||
Distribute a Submittal | ||||
Distribute the Submittals in a Package | ||||
Download a Submittal's Attachments | ||||
Download an Open Submittals Report | Complete this Task with the Reports Tool (Company Level) | |||
Edit a Custom Submittal Report | 2, 4 | 3, 4 | ||
Edit a Submittal | +6 | +6, 7 | ||
Edit a Submittal Package | ||||
Edit a Submittal Response | ||||
Enable Submittals Programme Calculations | ||||
Enable the Submittals Tool | ||||
Export a Custom Submittals Report | ||||
Export a Submittal | ||||
Export the Submittals Log | ||||
Finalise a Bluebeam Studio Session | 1 | |||
Forward a Submittal by Email | ||||
Forward a Submittal for Review | ||||
Generate a PDF of a Submittal in a List | ||||
Generate a QR Code for a Submittal | ||||
Manage Personal Submittal Markup Stamps | ||||
Manage Submittal Workflow Templates | ||||
Mark a Submittal as Private | ||||
Mass Review Submittals in a Package | ||||
Perform Bulk Actions on a Submittal | ||||
Redistribute a Submittal | ||||
Remove a Submitter or Approver from the Submittal Workflow | +8 | +8, 9 | ||
Resend the Submittals in a Package for Review | ||||
Resize the Column Width in the Submittals Log | ||||
Respond to a Forwarded Submittal as a Reviewer | ||||
Respond to a Submittal as an Approver | ||||
Respond to an Action Required Email for a Submittal Package as an Approver | ||||
Retrieve a Submittal from the Recycle Bin | ||||
Review Submittal PDF Attachments | ||||
Search and Filter for Submittals | ||||
Send a Completed Submittals Import Template to Procore | ||||
Send the Submittals in a Package for Review | ||||
Set Up Submittal Programme Calculations | ||||
Share a Custom Submittal Report | 2 | 3 | ||
Switch Between Submittals Views | ||||
Upload and Submit a Submittal | ||||
Use Bulk Actions > Apply Workflow in the Submittals Tool | ||||
Use Bulk Actions > Delete in the Submittals Tool | ||||
Use Bulk Actions > Edit in the Submittals Tool | ||||
Use Bulk Actions > Retrieve in the Submittals Tool | ||||
View a Submittal | 10 | 10 | ||
View a Submittal Package | ||||
View Submittal Attachments | ||||
View the Submittal Approvers Response Time Report |
1 Requires the Procore + Bluebeam Integration. See Bluebeam.
2 Users with 'Standard' level permission can only create personal reports.
3 Users with 'Admin' level permission can create, edit and view reports that have not been marked 'Personal' by another user.
4 Users will also need 'Read Only' level permission or higher on the Reports tool.
5 Users without 'Admin' level permissions on the project's Submittals tool can create revisions for submittals that they created.
6 Users without 'Admin' level permissions on the project's Submittals tool can edit certain fields in 'Draft' or 'Open' submittals that they created.
7 Users with 'Standard' level permissions can edit certain fields in submittals they are designated as the Submittal Manager. See What is the 'Submittal Manager' role?
8 Users without 'Admin' level permissions on the project's Submittals tool can update the submittal workflow in 'Draft' or 'Open' submittals that they created.
9 Users with 'Standard' level permissions can update the submittal workflow for submittals they are designated as the Submittal Manager. See What is the 'Submittal Manager' role?
10 When a submittal is marked 'Private', users with 'Read Only' or 'Standard' level permissions on the project's Submittals tool can see the submittal only if one or more statements apply:
- They are designated as the Submittal Manager
- They are added to the submittal workflow as a Submitter or an Approver.
- They are included in the distribution list.
- They have the 'View Private Submittals Associated to Users within Same Company' granular permission enabled on their permissions template and another user in their company is the submittal's creator or is designated as the Submittal Manager, a Submitter, an Approver or a Distribution List member.
Tasks
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 Comment to a Task | 1 | |||
Add a Task | 2 | |||
Change the Status of a Task | ||||
Configure Advanced Settings: Tasks | ||||
Delete a Task | ||||
Edit a Task | ||||
Export a Project's Task List | ||||
Search for and Filter Project Tasks | ||||
View a Task |
1 Users with 'Standard' level permissions can add comments to tasks they have created or when they have been designated as the task's assignee.
2 Users with 'Standard' level permissions can only assign tasks to users with 'Admin' level permissions to the Tasks tool.
Timesheets (Project Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Timesheets tool?
Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Crew to an Existing Timesheet |
|
|
|
||
Add Employees to a Timesheet you Created |
|||||
Add Employees to any Timesheet |
|
|
|||
Add Quantities to a Timesheet |
Users with 'Standard' level permissions can only add quantities to timesheets they have created. | ||||
Approve a Timesheet |
|||||
Bulk Enter Time in a Timesheet |
|
On a mobile device, this action can be performed offline. Tasks performed offline are synced with Procore when a network connection is reestablished. |
|||
Configure Advanced Settings: Project Level Timesheets |
|||||
Copy Previous Timesheet |
On a mobile device, this action can be performed offline. Tasks performed offline are synced with Procore when a network connection is reestablished. | ||||
Create a Timesheet |
|
|
|||
Delete a Timesheet |
|
|
Users with 'Read Only' level permissions can only delete 'Pending' timesheets.
|
||
Delete Budgeted Labour Hours and Budgeted Production Quantities |
'Admin' level permissions are required on the project's Admin tool to complete this action. | ||||
Delete Quantities on a Timesheet |
Users with 'Standard' level permissions can only delete quantities to timesheets they have created. | ||||
Edit Any Timesheet |
|||||
Edit a 'Pending' Timesheet |
|
|
|||
Edit a 'Reviewed' Timesheet |
|
||||
Edit a Timesheet You Created |
|||||
Edit a Pending Timesheet |
|
|
|||
Edit a Timesheet You Created |
|
||||
Edit Quantities on a Timesheet |
Users with 'Standard' level permissions must be the creator of ALL the quantities on the timesheet. | ||||
Export a Project's Timesheets |
|||||
Export the Field Production Report |
'Read-only' or higher level permissions are required on the project's Reports tool to complete this action. | ||||
Export the Labour Budget to Actual Report |
'Read-only' or higher level permissions are required on the project's Reports tool to complete this action. | ||||
Import Budgeted Hours |
'Admin' level permissions are required on the project's Admin tool to complete this action. | ||||
Import Budgeted Production Quantities |
|
'Admin' level permissions are required on the project's Admin tool to complete this action. | |||
Review a Timesheet |
|
|
|||
Search for and Filter Project Level Timesheets |
|||||
Set Up a Daily Reminder for Timesheets |
|||||
Set up a Field Production Report |
Additional permissions are needed to complete this action:
|
||||
Sign a Timesheet |
Permissions for this action are set in the company's Timecard tool. | ||||
Sign Timesheets for All Projects |
Permissions for this action are set in the company's Timecard tool. | ||||
View a Field Production Report |
'Read-only' or higher level permissions are required on the project's Reports tool to complete this action. | ||||
View a Labour Budget to Actual Report |
'Read-only' or higher level permissions are required on the project's Reports tool to complete this action. | ||||
View a Timesheet |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. | ||||
View a Timesheet Entry Signature |
|||||
View Quantities on a Timesheet |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
Daywork Sheets
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 Daywork Sheets | ||||
Create a T&M Ticket | ||||
Close or Reopen a T&M Ticket 2 | ||||
Configure Advanced Settings: Daywork Sheets | ||||
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 Daywork Sheet 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.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add Items to a Transmittal | ||||
Add Related Items to a Transmittal | ||||
Configure Advanced Settings: Transmittals | ||||
Create a Transmittal | ||||
Customise the Column Display in the Transmittals Tool | ||||
Delete a Transmittal | ||||
Edit a Transmittal | 1 | |||
Export a Transmittal Letter to PDF | ||||
Export a Transmittal Log to CSV | ||||
Export a Transmittal Log to PDF | ||||
Forward a Transmittal by Email | ||||
Resize Column Width in the Transmittals Log | ||||
Retrieve a Transmittal from the Recycle Bin | ||||
Search Transmittals | ||||
View a Transmittal | +2 | +2 | ||
View the Email Correspondence for a Transmittal |
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.