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)
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Create Calendar Items | |
|
||
| Configure Advanced Settings: Company Level Program | |
|||
| Search Project Programs | |
|
|
|
View All Schedule Tasks (for projects they have access to)  |
|
|
|
|
| View All Programmed Tasks for All Projects | |
Timecard
The following table highlights which user permissions are required to perform the described user action.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Configure Advanced Settings: Timecard | |
|||
| Configure Your Company For The Timecard | |
|||
| Create a Timecard 1 | |
|
||
| Edit a Timecard 1 | |
|
||
| Export a Timecards Report | |
|||
| Delete a Timecard 1 | |
|
||
| View the Change History of a Timecard | |
|||
| View a Timecard 1,2 | |
|
|
1 Users with 'Standard' level permissions can view, create, edit and delete their own timecards.
2 Users with 'Read Only' level permissions can only view their own timecards.
Timesheets (Company Level)
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 (Legacy) |
|
|
|
||
| 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 (Legacy) |
|
|
|
||
| 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 (Legacy) |
|
|
|
||
| Enable Classifications on a Project | |
||||
| Enable the DocuSign® Integration |
|
|
|
||
| Enable the Labour Productivity Cost Features for Project Financials | |
||||
| Export Locations (Legacy) |
|
|
|
||
| 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. | |||
|
|
|
|
|||
| Generate and Print QR Codes for Locations (Legacy) |
|
|
|
||
|
|
|
|
|||
| Import Segment Items into your Project Level Admin Tool | |
||||
| Import Spec Sections to the Admin Tool | |
||||
| 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 (Legacy) |
|
|
|
||
| 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 |
|
|
|
||
|
|
|
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 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 These steps require that your company has enabled the ProEst by Procore integration.
4 The Reports tool must be an active Project Tool. See Add and Remove Project Tools.
Change Events
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action that is supported by Procore for Android or Procore for iOS.
1 These tasks also require additional permissions on other tools in Procore. For more information, view the "Things to Consider" section in the tutorial for that action.
2 Users with 'Standard' permission can only delete the change events they create.
3 Users with 'Standard' permission can only edit the change events they create.
4 Users also need 'Standard' or 'Admin' level permissions on the Commitments tool.
5 Collaborators can submit a quote only if they receive an RFQ email notification. To be eligible to receive an email, the collaborator's user account must be granted 'Standard' level permissions on the project's Commitments tool and designated as the 'Assignee' on the RFQ. For details, see Assign and Send an RFQ to a Collaborator and Submit a Quote as a Collaborator.
Variations
The following table highlights which user permissions are required to perform the described user action.
1 To perform this task as a user with 'Standard' level permissions on the Variations tool, you must be the 'Designated Reviewer' on the variation. See Create a Commitment Variation.
2 Users with 'Admin' level permissions on the project's Variations tool must be granted additional tool permissions: (1) To edit a Commitment Variation (CV), 'Admin' level permissions on the project's Commitments tool, and/or (2) to edit a 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 on the item's correspondence type.
|
|
|
Edit a Correspondence Item Someone Else Created |
|
Shows permissions needed on the item's correspondence type. 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 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
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action supported in Procore's iOS and/or Android mobile application.
| Task | None | Read Only | Standard | Admin |
|---|---|---|---|---|
| Add a Worker 1, 2 |
|
|
||
| Create a Site team |
|
|
||
| Delete a Site Team | |
|||
| Edit a Site team 2 |
|
|
||
| Edit a Worker 1 |
|
|||
| Remove a Worker 3 | |
|||
| Search Site Teams | |
|
|
|
| Search for a Worker | |
|
|
|
| View a Site team |
|
|
|
|
| View a Worker |
|
|
|
1 Users must also be granted 'Read Only' or 'Standard' level permissions on the Project level Directory tool with the 'Create Contacts' granular permission enabled on their permission template OR must be granted 'Admin' level permissions on the Project level Directory tool to perform this task.
2 Users with 'Standard' permission can only edit a site team when designated as the 'Crew Lead'. See Create a Site team.
3 'Admin' users must also be granted 'Admin' permission on the project's Directory tool to perform this task.
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 Call 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 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 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. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Delivery Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Delivery Entries as a Collaborator |
|
|
|
||
|
Create 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 Equipment Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Inspection Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Working Hours 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 Working hours Entries as a Collaborator |
|
|
|
||
|
Create Note Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. |
||
|
Create Note Entries as a Collaborator |
|
|
|
||
|
Create Observed Weather Entries |
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | |||
|
Create Plan Revision Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Productivity Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Quantity Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Safety Violation Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Programmed Work Entries |
|
|
This action can be performed in offline. Tasks performed in offline mode will be synced with Procore once a network connection has been reestablished. | ||
|
Create Timecard Entries for Any User |
|
|
|||
|
Create Timecard Entries for Yourself |
|
|
Users with 'Standard' level permissions must also be marked as an employee of your company. |
||
|
Create Visitor Entries |
|
|
|||
|
Create Pending Visitor Entries as a Collaborator |
|
|
The granular permission for 'Collaborator Entry Only' has to be on a global template before the option is available in the Site Diary configuration settings. | ||
|
Create Waste Entries |
|
|
|||
|
Create a Change Event from a Site Diary Entry |
|||||
|
Create a Custom Report from the Site Diary |
|||||
|
Delete Any Site Diary Item |
|
Entries cannot be deleted on a day that has been marked as complete. If an entry needs to be deleted, an 'Admin' user can Re-Open a Site Diary. | |||
|
Delete a Site Diary Item You Created |
|
|
|
Entries cannot be deleted on a day that has been marked as complete. If an entry needs to be deleted, an 'Admin' user can Re-Open a Site Diary. |
|
|
Delete a Site Diary Item You Created as a Collaborator |
|
|
Entries cannot be deleted after they are approved by a Site Diary Admin.
|
||
|
Delete Related Items from Site Diary Entries |
|
||||
|
Edit Any Site Diary Item |
|
On 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 |
|