Commitments - User Permissions
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.
PROCORE SUPPORT: INTERNAL NOTES
Some Procore customers choose to grant downstream collaborators a higher level of permissions than documented in this matrix. Although this practice is supported, it is NOT recommended for the reasons stated below:
- 'Standard' level permissions on the project's Commitments tool. Although this permission gives designated progress claim contacts the ability to create progress claims with the Commitments tool, it also gives users permission to see ALL purchase orders and subcontracts that are NOT marked 'Private.' Because progress claim contacts are not employees of the company account managing the Procore project, it is recommended that users do NOT provide this permission to progress claim contacts.
- 'Admin' level permission on the project's Commitments tool. Although this permission gives users the ability to create progress claims, it gives the user full edit access to all of the commitments in the project's Commitments tool. It also gives the user permission to create progress claims before and after the 'Due Date.' Because progress claim contacts are not employees of the company account managing the Procore project, it is recommended that users do NOT provide this permission to progress claim contacts.
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.