User Permissions Matrix - Web
The following reference page is a comprehensive breakdown of all user actions and the specific user permissions (Read Only, Standard, and/or Admin) that are required to be able to perform that action. Since certain tools are available at both the Company and Project levels, be sure to select the appropriate navigational hyperlink below.
Company Level
Admin (Company Level)
The following table highlights which user permissions are required to perform the described user action.
- Indicates that the task can only be completed when Procore is configured to use the Company level ERP Integrations tool. See ERP Integrations.
* The user must have 'Admin' level permissions on both the Company and Project level Admin tools.
Conversations (Beta)
The following table highlights which user permissions are required to perform the described user action.
Note: The Conversations tool does not have its own set of permissions to assign and instead relies on users being part of a project's Directory and having access to items within that project. See the notes below the table for specific considerations.
1 The permission required for creating and managing a group depends on the 'Group Conversations Permissions' setting in the Company level Admin tool of the Procore account. See Configure Access and Settings for the Conversations Tool.
- If 'Administrators' is selected, 'Admin' level permissions to the Project or Company level Directory tool.
- If 'Internal Employees' is selected, users who are marked as internal employees. See How do I add someone as an employee of my company?
- If 'Everyone' is selected, any user in the Company Directory.
2 This action can be performed by any user in the project's Directory (for their own conversations and items that they have access to). See the specific considerations below:
- Direct Messages:
- If Direct Messages are enabled for the account, anyone in the project's Directory (and Company Admins) can be messaged or mentioned.
- If Direct Messages are only enabled for internal employees, only users marked as employees of the company can be messaged or mentioned. See How do I add someone as an employee of my company?
- Direct messages are private and can only be seen by the individuals in the message. Admin users cannot view direct messages that they are not a part of.
Note: A data export containing direct messages can be provided to Company Admins by Procore Support if needed.
- Group Conversations:
- Anyone in the project's Directory (and Company Admins) can be messaged or mentioned in a group.
- Messages within a group conversation can only be seen by members of that group.
- Item Conversations:
- Conversations for specific items in a project can only be viewed and participated in by users with access to the item in Procore ('Read Only' or higher permissions to the item's tool and appropriate access if an item is marked as Private).
- All conversations:
- Users can only message or mention users who exist in the project's Directory, as well as Company Admins.
- Users can only edit and delete their own messages (within 5 minutes of sending and if the feature is enabled).
- Users can only hide a conversation from their own view.
Cost Catalogue
The following table highlights which user permissions are required to perform the described user action.
Directory (Company Level)
Important
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 this action with this permission level AND one or more additional requirements, like 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 |
|---|---|---|---|---|---|
|
Accept or Deny a User's Request to Join Your Company |
|
||||
|
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)
Important
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 this action with this permission level AND one or more additional requirements, like 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 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 Project Groups | * |
|||
| Add a Project to a Project Group | * |
|||
| Assign a Project to a Different Project Group | * |
|||
| Delete a Project Group | * |
|||
| Edit Project Group Information | * |
|||
| Remove a Project from a Project Group | * |
|||
| View Project Groups | |
|
|
* 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.
Program (Company Level)
Important
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 this action with this permission level AND one or more additional requirements, like granular permissions.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Configure Advanced Settings: Company Level Program |
|
  |
|||
|
Search Project Programs
|
|
|
|
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)
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 this action with this permission level AND one or more additional requirements, like 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?'.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Configure Advanced Settings: Company Level Timesheets |
|
||||
|
Configure the Company Timesheets Payroll Settings |
|
||||
|
Customise the Column Display in the Company Level Timesheets Tool |
|
|
|
||
|
Delete a Timecard Entry in the Company Level Timesheets Tool You Created |
|
|
|||
|
Delete Any Timecard Entry in the Company Level Timesheets Tool |
|
||||
|
Duplicate Your Company's Timesheets in Bulk |
|
||||
|
Edit a Timecard Entry in the Company Level Timesheets Tool You Created |
|
|
|||
|
Edit Any Timecard Entry in the Company Level Timesheets Tool |
|
||||
|
Edit Your Company's Timesheets in Bulk |
|
||||
|
Export Timecard Entries from Procore to Import into QuickBooks® Desktop |
|
|
|||
|
Export Timesheet Data from Procore into Sage 300 CRE® |
|
|
|||
|
Export Your Company's Timecard Entries to CSV |
|
|
|
||
|
Import Procore Time Entries into QuickBooks® Desktop |
|
|
|||
|
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 |
|
|
|||
|
Reallocate Timecard Entry Hours for an Employee |
|
|
|||
|
Search and Filter Time Entries in the Company Level Timesheets Tool |
|
|
|
||
|
Set the Rounding Rule for Your Company Timesheets |
|
||||
|
Transfer Procore Timecard Entries to QuickBooks® Desktop |
|
|
|
|
|
|
View a Timecard Entry in the Company Level Timesheets Tool |
|
|
|
|
|
|
View Timecard Summaries in the Company Level Timesheets Tool |
|
|
|
|
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)
Important
| | 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 this action with this permission level AND one or more additional requirements, like granular permissions.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
| Activate Budget Codes on a Project |
|
|
|
||
| Add a Project to a Project Group |
|
|
|||
| Add and Remove Project Tools |
|
|
|
||
| Add Custom Segments to the Project Budget Code Structure | |
||||
| Add Equipment | |
||||
| Add Segment Items to a Project |
|
|
|
|
|
| Add Spec Sections to the Admin Tool | |
||||
| Add Sub Job Segment Items to a Project |
|
|
|
||
| Add Tiered Locations to a Project |
|
|
|
||
| Allow or Disallow Users to Create Locations within a Tool | |
||||
| Arrange the Project Budget Code Structure |
|
|
|
||
| Assign an Office Location to a Project |
|
|
|
||
| Assign a Project to a Different Project Group |
|
|
|
||
| Assign Project Cost Codes to Sub Jobs | |
||||
| Change a Project's Status to Active or Inactive |
|
|
|
||
| Change Your Project's Stage of Construction |
|
|
|
||
| Change the Name of a Procore Project |
|
|
|
||
| Change the Project Address |
|
|
|
||
| Configure General Settings: Project Admin |
|
|
|
||
| Configure Project Webhooks | |
||||
| Copy Company Cost Codes to a Project |
|
|
|
||
| Copy Company Segments to a Project | |
||||
| Copy People From One Project to Another |
|
|
|
||
| Create Your Project's Work Breakdown Structure | |
||||
| Deactivate Budget Codes on a Project |
|
|
|
||
| Delete Tiered Location from a Project |
|
|
|
||
| Delete Spec Sections from the Admin Tool | |
||||
| Delete Sub Jobs from a Project |
|
|
|
||
| Delete Unused Segment Items from a Project |
|
|
|
Your Procore Administrator must configure additional settings for you to edit or delete a custom segment. See Admin: Manage WBS Codes. | |
| Edit an Existing Budget View | |
||||
| Edit or Add General Project Information |
|
|
|
||
| Edit Segment Items on a Project |
|
|
|
Procore's default 'Cost Type' segment can only be managed by a user with 'Admin' permissions to the Company level Admin tool. Your Procore Administrator must configure additional settings for you to edit or delete a custom segment. See Admin: Manage WBS Codes. |
|
| Edit Spec Sections in the Admin Tool | |
||||
| Edit Sub Jobs on a Project |
|
|
|
||
| Edit Tiered Locations |
|
|
|
||
| Enable Classifications on a Project | |
||||
| Enable the DocuSign® Integration |
|
|
|
||
| Enable the Labour Productivity Cost Features for Project Financials | |
||||
| Export Locations |
|
|
|
||
| Export WBS Segments to CSV |
|
|
|
||
| Extract Project Data Using Procore Extracts | |
You must also have Admin level permissions to the Project level tool you want to extract data from. | |||
| Filter Locations |
|
|
|
You must also have access to view the item within the tool. | |
|
|
|
|
|||
| Generate and Print QR Codes for Locations |
|
|
|
||
| Import Segment Items into your Project Level Admin Tool | |
||||
| Import Spec Sections to the Admin Tool | |
||||
| Manually Create Locations |
|
|
|
||
| Rearrange the Tool's in the Project Toolbox |
|
|
|
||
| Remove a Project from a Project Group |
|
|
|
||
| Remove Segments from the Project Budget Code Structure | |
||||
| Request to Import Segment Items | |
||||
| Request a Multi-tiered Locations Import |
|
|
|
||
| Search Locations | |
|
|
||
| Set the Project Type |
|
|
|
||
| Set Up a Labour Budget to Actual Report for the Timesheets Tool | |
The Project level Timesheets tool must also be enabled. 'Admin' level permissions to the Project Directory tool are required to perform an import that is part of the setup process. |
|||
| Set User Permissions for the Project Admin Tool | |
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. | |||
| Upload a Project Logo |
|
|
|
||
| View Item Locations |
|
|
 |
You must also have access to view the item within the tool. | |
|
|
|
Users with Read Only or Standard level permissions can only view locations that are published, unless those users also have the Manage Locations granular permission. | ||
| View Locations Heat Map |
|
|
|
||
| View Project Insights | |
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 action.
5 These tasks are performed by tenderers using the Company level Planroom tool. See Planroom.
6 Users with 'Read Only', 'Standard' or 'Admin' level permissions to the project's Tendering tool AND assigned as the Blind Tendering Manager on a tender package can complete this action.
7 Users with 'Read Only' or 'Standard' level permissions to the project's Tendering tool are NOT able to edit tender values. However, they may still view and download tender attachments.
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 Head Contracts tool.
2 Also requires 'Admin' permissions on the Company level Reports tool.
3 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 Head Contract Variation (HCV), 'Admin' level permissions on the project's Head 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 Head 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 progress claim contact on the commitment. See Add Progress Claim 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 Progress Claim Contact. See Add Progress Claim 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 SOV Items' check box 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 progress claim 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
Important
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 this action with this permission level AND one or more additional requirements, like granular permissions.
What granular permissions are available for the project's Correspondence tool?
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add a Related Item to a Correspondence Item |
|
|
Standard users can perform this task for correspondence items that they created. | ||
|
Archive a Correspondence Item |
|
||||
|
Change the Status of a Correspondence Item You Created |
|
|
|
Users with 'Read Only' level permissions need 'Create Item' granular permissions to change the status of a 'Draft' item that they created. Users with 'Read Only' level permissions need 'Edit Open Items They Create' granular permissions to change the status of an 'Open' item that they created. |
|
| Change the Status of a Correspondence Item Someone Else Created Web |
|
||||
|
Complete a Correspondence Item with DocuSign® |
|
Admin permissions needed on the correspondence type for which you want to initiate, download or withdraw a DocuSign®. | |||
|
Configure Advanced Settings: Correspondence |
|
||||
|
Create a Correspondence Item |
+ Create Item |
|
|
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore when a network connection is reestablished. | |
|
Create and Link a New Correspondence Item from a Correspondence Response |
+ Create Item |
+ Create Item |
|
These are the permission levels needed on the correspondence type used to create the new item. | |
| Create and Link an RFI to an Existing Correspondence Item Web |
|
|
|
All levels need additional permissions in the project's RFI tool: Create and link a 'Draft' RFI: |
|
| Create and Link a Change Event to an Existing Correspondence Item Web |
|
|
|
All levels need additional permissions: 'Standard' level permissions or higher in the project's Change Events tool. |
|
| Create and Link a Correspondence Item to an Existing Correspondence Item Web |
|
|
|
All levels need additional permissions in the new item's correspondence type: 'Read Only' level permissions on the new item's correspondence type with the 'Create Item' granular permissions enabled on your permissions template. OR 'Standard' level permissions or higher on the new item's correspondence type. |
|
| Customise the Column Display in the Correspondence Tool Web |
|
|
|
||
|
Edit a Correspondence Item You Created
|
+Create Item (for 'Draft' Items) OR + Edit Open Items They Created (for 'Open' Items) |
|
|
Shows permissions needed for each correspondence type. If the 'non-editable' setting is enabled (by Procore) at the company level, the granular permission 'Edit Open Items they Created' is not available because 'Open' and 'Closed' items cannot be edited by any user or Admin.
|
|
|
Edit a Correspondence Item Someone Else Created |
|
Shows permissions needed for each correspondence type. If the 'non-editable' setting is enabled (by Procore) at the company level, it is not possible for any user or Admin to edit a correspondence item that someone else created. |
|||
| Export a Correspondence Item Web |
|
|
|
User needs access to a correspondence item for this task. See View a Correspondence Item. | |
| Export a List of Correspondence Items Web |
(Excludes correspondences marked as Private) |
(Excludes correspondences marked as Private) |
|
Learn about Super Private to explore more restrictions on Admin level permissions. | |
| Generate a QR Code for a Correspondence Item Web |
|
|
|
User needs access to a correspondence item for this task. See View a Correspondence Item. | |
| Link a Correspondence Item on your personal layer on a drawing Web |
|
|
|
All levels need additional permissions: |
|
| Link a Correspondence Item and publish the markups to the drawing Web |
|
|
|
Additional permissions needed in Drawings tool: |
|
| Perform Bulk Actions on Correspondence Items Web |
|
||||
|
Respond to a Correspondence Item |
|
|
|
On a mobile device, this action can be performed offline. Tasks performed offline sync with Procore when a network connection is reestablished. * In addition to this granular permission, users must be the item's creator or added to the item's 'Assignee' field, 'Received From' field, or 'Distribution' list. **In addition to this granular permission, users must be associated with the same company as the item's creator or added to the item's 'Assignee' field, 'Received From' field, or 'Distribution' list. |
|
| Access Workflow information and actions |
|
|
|
To learn more about the Workflows tool see About the Workflows. | |
| Scan a Correspondence Item QR Code iOS Android |
|
|
|
User needs access to the correspondence item for this task. See View a Correspondence Item. | |
|
Search, Sort and Filter Correspondences |
|
|
|
Users can perform these actions for each correspondence type they have read-only or higher permissions for. On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore when a network connection is reestablished. |
|
| View a Correspondence Item |
|
|
|
Users may need specific roles or granular permissions to view an item depending on the item's status and privacy setting. Expand the Tip box on View a Correspondence Item to learn more. |
Site teams
Important
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 this action with this permission level AND one or more additional requirements, like granular permissions.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add a Worker |
|
|
|
||
|
Create a Site Team |
|
|
|||
|
Delete a Site team |
|
||||
|
Edit a Site Team |
|
|
Users with 'Standard' level permissions must also be designated as the 'Crew Lead' to take this action. On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore when a network connection is reestablished. |
||
|
Edit a Worker |
|
Users must also have the following permissions for the project's Directory Tool to take this action:
|
|||
|
Remove a Worker |
|
Users must also have 'Admin' level permissions on project's Directory tool to take this action. | |||
|
Search Site Teams |
|
|
|
||
|
Search for a Worker |
|
|
|
||
|
View a Site Team |
|
|
|
||
|
View a Worker |
|
|
|
Site Diary
Important
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 this action with this permission level AND one or more additional requirements, like 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 Register 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 Pending Accident Register Entries as a Collaborator |
|
|
|
||
|
Create Phone Call 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 Pending Phone Call Entries as a Collaborator |
|
|
|
||
|
Create Daily Construction Report Register 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 Pending Daily Construction Report Register 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 mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Pending Delay Entries as a Collaborator |
|
|
|
||
|
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 Pending Delivery Entries as a Collaborator |
|
|
|
||
|
Create Skip 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 Pending Skip Entries as a Collaborator |
|
|
|
||
|
Create Equipment Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Pending Equipment Entries as a Collaborator |
|
|
|
||
|
Create Inspection Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Inspection Entries as a Collaborator |
|
|
|
||
|
Create Working Hours Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Working hours Entries as a Collaborator |
|
|
|
||
|
Create Note Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Pending Note Entries as a Collaborator |
|
|
|
||
|
Create Observed Weather Entries |
|
This action can be performed in offline mode. 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 mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Plan Revision Entries as a Collaborator |
|
|
|
||
|
Create Productivity Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Productivity Entries as a Collaborator |
|
|
|
||
|
Create Quantity Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Quantity Entries as a Collaborator |
|
|
|
||
|
Create Safety Violation Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Safety Violation Entries as a Collaborator |
|
|
|
||
|
Create Programmed Work Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Programmed Work Entries as a Collaborator |
|
|
|
||
|
Create Timecard Entries for Any User |
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
|||
|
Create Timecard Entries for Yourself |
|
|
|
||
|
Create Visitor Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Visitor Entries as a Collaborator |
|
|
|
||
|
Create Waste Entries |
|
|
This action can be performed in offline mode. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Pending Waste Entries as a Collaborator |
|
|
|
||
|
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 a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore when a network connection is reestablished. |
|||
|
Edit a Site Diary Item You Created |
|
|
On a mobile device, this action can be performed offline. Tasks performed offline sync with Procore when a network connection is reestablished. | ||
|
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 |
|
||||
|
Reject Any Site Diary Entry Created by Collaborators |
|
||||
|
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 Register |
|
|
|||
|
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)
Important
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 this action with this permission level AND one or more additional requirements, like 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 |
|
|
|
||
|
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 from the Company 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 Template in the 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 Manually in the Project Directory |
|
||||
|
Configure the Project Team on the Project Home Page |
|
|
|
||
|
Configure Advanced Settings for the Project Directory: Edit Permissions |
|
||||
|
Configure Advanced Settings for the Project Directory: Edit Project Roles |
|
|
|
||
|
Configure the Project Team on the Project Overview Page |
|
|
|
||
|
Configure Program Notification Emails |
|
Users also need 'Admin' level access to the project's Program tool. | |||
|
Create a Project Specific Permissions Template from the Project Directory |
|
||||
|
Create a User Account in the Project Directory |
|
|
|
||
|
Customise the Column Display in the Directory Tool |
|
|
|
||
|
Deactivate a Company in the Project Directory |
|
|
|
||
|
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 a User's Default Email Notifications |
|
|
|
||
|
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 Program 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 |
|
|
|
||
|
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 |
|
|
|
||
|
Request Company and People Imports |
|
|
|||
|
Save Contact to Phone on a Mobile Device |
|
|
|
||
|
Search and Filter Active Users, Contacts, and Companies in the Project Directory |
|
|
|
||
|
Search and Filter Inactive Users, Contacts, and Companies in 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 Active Users, Contacts, and Companies in 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. | |
|
View Inactive Users, Contacts, and Companies in the Project Directory |
|
||||
|
View Company Insurance Information |
|
|
|
Documents (Project Level)
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 this action with this permission level AND one or more additional requirements, like 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.
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
Important
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 this action with this permission level AND one or more additional requirements, like granular permissions.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add 3D Model Takeoffs |
|
|
Users also need 'Read Only' level permissions or higher to the project's Models tool. | ||
|
Add 3D Model Takeoffs Using Auto-Mapping |
|
|
Users also need 'Read Only' level permissions or higher to the project's Models tool. | ||
|
Add an Estimate |
|
|
|||
|
Add and Manage Internal Notes in a Tender Board Project |
|
|
|||
|
Add and Manage Tasks in a Tender Board Project |
|
|
|||
|
Add Inclusions and Exclusions |
|
|
|||
|
Add Items to a Cost Catalogue |
|
|
Users also need 'Standard' level permissions or higher to the Company level Cost Catalog tool. | ||
|
Add a Variation for an Estimate |
|
|
Users also need 'Standard' level permissions or higher to the Project level Change Events tool. | ||
|
Assign a Budget Code from an Estimate |
|
|
|||
|
Configure Estimating Tool Settings |
|
Users with Admin level permissions to the company's Admin tool manage additional settings in the company's Admin tool. | |||
|
Configure Settings for an Estimate in the Estimating Tab |
|
|
|||
|
Copy a Group to Another Project |
|
||||
|
Copy or Move a Group to Another Estimate |
|
||||
|
Copy a Takeoff Group |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Copy Takeoff Layers |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Create a Head Contract from an Estimate |
|
Users also need 'Admin' level permissions or higher to the Project level Budget tool. | |||
|
Create a Purchase Order from an Estimate |
|
Users also need 'Admin' level permissions or higher to the Project level Budget tool. | |||
|
Delete Documents from a Tender Board Project |
|
|
|||
|
Delete a Takeoff Group |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Delete Takeoff Layers |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Download Documents from a Tender Board Project |
|
|
|
||
|
Edit a Tender Proposal with the Proposal Builder |
|
|
|||
|
Edit an Estimate |
|
|
|||
|
Edit Custom Fields for a Tender Board Project |
|
|
|
||
|
Edit Customer Information for a Tender Board Project |
|
|
|||
|
Edit the Estimate Overview for a Tender Board Project |
|
|
|||
|
Expand or Collapse Takeoff Groups |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Export a Tender |
|
|
|
||
|
Export an Estimate |
|
|
|||
|
Generate a Tender Proposal |
|
|
|||
|
Lock and Unlock Takeoff Layers |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Manage Inclusion and Exclusion Libraries |
|
|
|||
|
Merge Estimates |
|
|
|||
|
Move Takeoff Layers to a New Group |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Rename a Takeoff Group |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Respond to a Tender Invitation |
|
|
|||
|
Run Automated Area Takeoffs |
|
|
Users also need 'Read Only' level permissions or higher to the project's Models tool. | ||
|
Search for Model Objects in Estimating |
|
|
Users also need 'Read Only' level permissions or higher to the project's Models tool. | ||
|
Send a Variation to the Change Events Tool |
|
|
Users also need 'Standard' level permissions or higher to the Project level Change Events tool. | ||
|
Send an Estimate to the Budget |
|
Users also need 'Admin' level permissions or higher to the Project level Budget tool. | |||
|
Set the Drawing Scale for Takeoffs |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Show or Hide Takeoff Layers |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Split Takeoff Layers |
|
|
Users also need 'Standard' level permissions or higher to the project's Drawings tool. | ||
|
Upload Documents from a Tender Board Project |
|
|
|
||
|
View 3D Models in Estimating |
|
|
Users also need 'Read Only' level permissions or higher to the project's Models tool. | ||
|
View an Estimate |
|
|
|
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.
Incidents
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action that is supported in Procore's iOS and/or Android mobile application.
1 'Standard' users can edit assets in incidents that they create.
2 'Standard' users can only email incidents that they create.
Inspections (Project Level)
Important
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 this action with this permission level AND one or more additional requirements, like 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 Conditional Logic to a Project Level Inspection Template |
|
||||
|
Add Attachments to Inspection Items |
|
|
|
||
|
Add Signers to an Inspection |
|
|
|
||
|
Add Signers to an Inspection Item |
|
|
On an iOS mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
||
|
Clone a Project Inspection Template to a Company |
|
||||
|
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 Program |
|
|
|
||
|
Delete an Inspection Template |
|
||||
|
Edit an Inspection You Created |
|
|
On an Android mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
||
|
Edit Any Inspection |
|
On an Android mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
|||
|
Edit a Project Level Inspection Template |
|
||||
|
Edit an Inspection Program |
|
|
|
||
|
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 a Completed 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. | ||
|
Sign an Inspection Item |
|
|
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.
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.
Meetings
Important
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 this action with this permission level AND one or more additional requirements, like 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 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 this action with this permission level AND one or more additional requirements, like granular permissions.
Note
'Standard' level permission does not exist for the Models tool.| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add a Section Box to a Model |
|
Users also need 'Read Only' or higher level permissions to the Drawings tool to map a 2D sheet to a model. | |||
|
Associate a Model with a Procore Project |
|
||||
|
Create a Co-ordination Issue in the Model Viewer |
|
Users also need 'Standard' or 'Admin' level permissions to the Co-ordination Issues tool. | |||
|
Create an Observation in the Model Viewer |
|||||
|
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 |
|
Users also need 'Standard' or 'Admin' level permissions to the Co-ordination Issues tool. | |||
|
Measure Distances on a Model |
|||||
|
Publish a Model to Procore |
|
Users also need 'Read Only' or higher level permissions to the Drawings tool to map a 2D sheet to a model. | |||
|
Publish a New Version of a Model |
|
Users also need 'Read Only' or higher level permissions to the Drawings tool to map a 2D sheet to a model. | |||
|
Reassociate a Model with a Procore Project |
|
||||
|
Search for and Filter Co-ordination Issues in the Model Viewer |
|
|
Users also need 'Read Only' or higher level permissions to the Co-ordination Issues tool. | ||
|
Search for and Sort Models |
|
|
|||
|
Use the Section Tool on a Model |
|
|
|||
|
View a Model |
|
|
|||
|
View the Version History of 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.
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.
1 Users with 'Standard' level permissions on the project's Photos tool may only bulk edit photo descriptions.
Head 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.
1 Users with 'Standard' level permissions can only create a PV if the 'Allow Standard Level Users to Create PVs' checkbox is enabled in the Configure Settings page. For more information, see Configure Advanced Settings: Head Contract.
2 Users with 'Read Only' and 'Standard' level permissions can only view a head contract that is private if they have been added to the 'Private' drop-down list on the head 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.
Defect 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.
1 Users with 'Standard' level permissions can perform this action if they are listed as the item's Defect Item Manager, Assignee or Final Approver or if they have been granted the granular permission "Respond to Defect Items Assigned to Users within the Same Company."
2 While 'Standard' level users can create defect list items, they cannot assign a defect list item unless they have been granted special permission to act as the Defect Item Manager. See Grant a Standard User Permissions to Act as a Defect List Manager.
3 'Standard' level users can only close defect 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 'Defect Item Manager'.
4 Users with 'Read Only' permissions can perform this action if they have been granted the granular permission “Respond to Defect Items Assigned to Users within the Same Company.”
5 Users with 'Standard' and 'Read Only' permissions can only view non-private defect 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 | 3 |
|||
| View User Sessions Reports | 3 |
|||
| View Outbound Emails Report | |
|||
| View RFI Delays | 3 |
3 |
3 |
|
| View Submittal Approvers' Response Time | 3 |
3 |
3 |
|
| View Defect 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 Head Contract Variations | |
|
|
|
| View Committed Cost Report | |
|
|
|
| View Overdue Commitment Variations | |
|
|
|
| View Subcontractor Progress Claims by Date | |
|
|
|
| View Unexecuted Head Contract Variations | |
|
|
|
| View Head Potential Variation Report By Change Reason | |
|
|
|
| View Monitored Resources Report | 5 |
5 |
5 |
| Program Reports | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| View All Program 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 |
|---|---|---|---|---|---|
| Action Plan | Action Plans | |
|||
| Action Plan Approver | Action Plans | |
|||
| Action Plan Line Item | Action Plans | |
|||
| Action Plan Line Item Assignee | Action Plans | |
|||
| Action Plan Line Item Record | Action Plan | |
|||
| Action Plan Line Item Record Request | Action Plans | |
|||
| Action Plan Line Item Reference | Action Plans | |
|||
| Action Plan Receiver | Action Plan | |
|||
| 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 | |
|
|
|
| Co-ordination Issue | Co-ordination Issues | |
|
|
|
| Correspondence | Correspondence | 1 |
|||
| Correspondence Assignee | Correspondence | 1 |
|||
| Correspondence Distribution List | Correspondence | 1 |
|||
| Correspondence Response | Correspondence | 1 |
|||
| Site team | Site teams | |
|
|
|
| Site Diary Accident | Site Diary | |
|||
| Site Diary Completion | Site Diary | |
|||
| Site Diary Construction Report | Daly Log | |
|||
| Site Diary Delay | Site Diary | |
|||
| Site Diary Delivery | Site Diary | |
|||
| Site Diary Skip | Daly Log | |
|||
| Site Diary Equipment | Site Diary | |
|||
| Site Diary Inspection | Site Diary | |
|||
| Site Diary Working hours | Daly Log | |
|||
| Site Diary Note | Site Diary | |
|||
| Site Diary Observed Weather Condition | Site Diary | |
|||
| Site Diary Phone Call | Daly Log | |
|||
| Site Diary Plan Revision | Site Diary | |
|||
| Site Diary Productivity | Site Diary | |
|||
| Site Diary Quantity | Daly Log | |
|||
| Site Diary Safety Violation | Site Diary | |
|||
| Site Diary Programmed Work | Site Diary | |
|||
| Site Diary Programmed Work Task | Daly Log | |
|||
| Site Diary Visitor | Site Diary | |
|||
| Site Diary Waste | Site Diary | |
|||
| Direct Cost | Direct costs | |
|
|
|
| Direct Cost Line Item | Direct costs | |
|
|
|
| Distribution List | RFI | |
|||
| Drawing Revision | Drawing | |
|
|
|
| Drawing Markup Link | Drawing | |
|
|
|
| Employees | Directory | |
|
|
|
| ERP Job Costs Summary | Budget | |
|
|
|
| Form | Forms | |
|||
| Incident | Incident | |
|||
| Incident Action | Incident | |
|||
| Incident Alert | Incident | |
|||
| Incident Distribution Member | Incident | |
|||
| Incident Injury Body Part | Incident | |
|||
| Incident Record | Incident | |
|||
| Inspection | Inspection | |
|||
| Inspection Assignee | Inspection | |
|||
| Inspection Distribution List | Inspection | |
|||
| Inspection Item | Inspection | |
|||
| Inspection Item Activity | Inspection | |
|||
| Inspection Item Comment | Inspection | |
|||
| Inspection Program | Inspection | |
|||
| Inspection Program Assignee | Inspection | |
|||
| Inspection Program Distribution List | Inspection | |
|||
| Inspection Signature Request | Inspection | |
|||
| Instructions | Instructions | |
|||
| Labour Productivity |
Budget OR timesheets |
|
|
|
|
| Labour Productivity: Budget | Budget | |
|
|
|
| Location | N/A | |
|
|
|
| Meeting | Meeting | |
|||
| Meeting Attendee | Meeting | |
|||
| Meeting Item | Meeting | |
|||
| Meeting Item Assignee | Meeting | |
|||
| Meeting Item Attendee | Meeting | |
|||
| Monitored Resource | Budget | |
|
|
|
| Observation | Observation | |
|||
| Observation Activity | Observation | |
|||
| Observation Distribution Member | Observation | |
|||
| Owner Progress Claim | Head contracts | |
|||
| Owner Progress Claim Line Item | Head contracts | |
|||
| Photo | Photo | |
|||
| Defect Item | Defect List | |
|||
| Defect Item Assignee | Defect List | |
|||
| Defect Item Ball in Court | Defect List | |
|||
| Defect Item Comments | Defect List | |
|||
| Defect Item Distribution Member | Defect List | |
|||
| Head Contract | Head contracts | |
|||
| Head Contract Variation | Head contracts | |
|||
| Head Contract Variation Line Item | Head contracts | |
|||
| Head Contract Variation Markup | Head contracts | |
|||
| Head Contract Variation Request | Head contracts | |
|||
| Head Contract Variation Workflow Responses | Head contracts | |
|||
| Head Contract Variation Workflow Steps | Head contracts | |
|||
| Head Contract Line Item | Head contracts | |
|||
| Head Contract Potential Variation | Head contracts | |
|||
| Head Potential Variation Production Quantity | Head contracts | |
|
|
|
| Head Workflow Responses | Head contracts | |
|||
| Head Workflow Steps | Head 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 | |
|||
| Program Calendar Item | Program | |
|||
| Program Lookahead | Program | |
|
|
|
| Program Lookahead Task | Program | |
|
|
|
| Program Task | Program | |
|
|
|
| Program Task Request | Program | |
|
|
|
| Specifications | Specifications | |
|
|
|
| Sub Progress Claim Workflow Responses | Commitments | |
|||
| Sub Progress Claim Workflow Steps | Commitments | |
|||
| Subcontractor Progress Claim | Commitments | |
|||
| Subcontractor Progress Claim Line Item | Commitments | |
|||
| Submittal | Submittal | |
|||
| Submittal Approver | Submittal | |
|||
| Submittal Ball In Court | Submittal | |
|||
| Submittal Distribution List | Submittal | |
|||
| Daywork Sheet | Daywork Sheets | |
|
|
|
| Daywork Sheet Equipment | Daywork Sheets | |
|
|
|
| Daywork Sheet Labour | Daywork Sheets | |
|
|
|
| Daywork Sheet Material | Daywork Sheets | |
|
|
|
| Task | Task | |
|||
| Task Activity | Task | |
|||
| Task Assignee | Task | |
|||
| Timecard Entry | Timesheets | |
|
|
1 Correspondence Type Admins can access all Correspondence field sets and are limited to columns and rows of data by correspondence types. Super Private Correspondence records are not available in Enhanced Reporting.
Permissions for Datasets
Access to datasets is determined by access to field groups within a dataset. In order to be granted access to a dataset, a user must have access to one of the field groups within the given dataset. The user will still only have access to the data within the field groups which they have access.
| Dataset | Field Group |
|---|---|
| Financials | Budget Line Items, Head Contract, Commitments, Change Events, Direct Costs |
| Project Execution | Action Plan, Correspondence, Co-ordination Issue, Site Diary, Drawing, Form, Incident, Inspection, Meeting, Observation, Photo, Defect List, RFI, Program, Submittal or Task |
| Workforce Management | Budget Line Items, Head Contract, Commitments, Change Events, Direct Costs, Site teams, Time & Material or 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.
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 head contract must be in the 'Approved' status, the Change Events tool must be disabled on the project and the Head 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.
Program (Project Level)
Important
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 this action with this permission level AND one or more additional requirements, like granular permissions.
What granular permissions are available for the Project level Program tool?
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add Related Items to a Programmed Task |
|
||||
|
Configure Advanced Settings: Program |
|
||||
|
Configure Program Notification Emails |
|
||||
|
Configure the Project Level Program Tool for Primavera P6 |
|
||||
|
Clear an Integrated Program |
|
||||
|
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 |
|
|
|
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. Tasks performed offline sync with Procore when a network connection is reestablished. | |
|
Export a Project Program |
|
|
|||
|
Request a Program Change |
|
|
|||
|
Search and Filter for Programmed Tasks |
|
|
|
||
|
Send Recurring Project and Resource Programs |
|
||||
|
Update a Project Program File |
|
||||
|
Update Lookahead Tasks |
|
|
|
||
|
Update Task Completion Percentage |
|
|
|
||
|
Upload a Project Program File to Procore's Web Application |
|
||||
|
Upload an Asta Powerproject Program |
|
||||
|
View a Project Program |
|
|
|
||
|
View a Programmed Task |
|
|
|
||
|
View Lookahead |
|
|
|
||
|
View the Change History of Lookaheads |
|
|
|
Specifications
Important
| | 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 this action with this permission level AND one or more additional requirements, like granular permissions.
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add a Related Item to a Specification |
|
||||
|
Configure Advanced Settings: Specifications |
|
||||
|
Create a Specification Set |
|
||||
|
Delete Pending Specification Uploads |
|
||||
|
Delete Specification Section Revisions |
|
||||
|
Download Specifications |
|
|
|
||
|
Edit Specification Sections and Divisions |
|
||||
|
Email Specifications |
|
|
|||
|
Export Specifications as a PDF or CSV |
|
|
|
||
|
Manually Create Divisions |
|
||||
|
Manually Create Specification Sections |
|
||||
|
Mark Specifications as Obsolete |
|
||||
|
Review and Publish Specifications |
|
||||
|
Search and Filter for Specifications |
|
|
|
||
|
Submittal Builder: Add Submittals |
|
|
|
Users must also have 'Admin' level permission on the project's Submittals tool. | |
|
Submittal Builder: Configure Submittal Titles |
|
|
|
Users must also have 'Admin' level permission on the project's Submittals tool. | |
|
Submittal Builder: Generate Submittals from Specifications |
|
|
|
Users must also have 'Admin' level permissions to the Submittals tool. | |
|
Upload Specification Revisions |
|
||||
|
Upload Specifications |
|
||||
|
View a Deleted Specifications Report |
|
||||
|
View Report of All Specification Revisions |
|
|
|
||
|
View Specifications |
|
|
|
||
|
View Change History for Specifications |
|
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.
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.
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)
Important
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 this action with this permission level AND one or more additional requirements, like granular permissions.
What granular permissions are available for the Project level Timesheets tool?
| Action | None | Read Only | Standard | Admin | Notes |
|---|---|---|---|---|---|
|
Add a Site team to an Existing Timesheet You Created |
 |
|
|
||
|
Add a Site team to any Existing Timesheet |
|
|
|
|
|
|
Add Employees to a Timesheet you Created |
|
|
|||
|
Add Employees to any Timesheet |
|
|
|
||
|
Add Quantities to a Timesheet you Created |
|
|
|||
|
Add Quantities to Any Timesheet |
|
||||
|
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 You Created |
|
|
|
|
|
|
Delete Any Timesheet |
|
|
|||
|
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 a 'Pending' Timesheet |
|
|
|
Users with granular permissions can in line edit one timesheet at a time. | |
|
Edit a Timesheet You Created |
|
|
|
||
|
Edit Any Timesheet |
|
||||
|
Edit the Status of a 'Reviewed' Timesheet |
|
|
|
||
|
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 a Unit Quantity Based Budgeted |
|
'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 Private Timesheet You Created or are Assigned |
|
|
|
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 (not Private) |
|
|
|
|
|
|
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. | |
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.
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.