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 your company's Procore account must be configured to work with an integrated ERP system. 

Task	None	Read Only	Standard	Admin
Add a Line Item to a Commitment's Bill of Quantities
Add a New Payment to the Payments Issued Tab of a Commitment
Add a Related Item to a Purchase Order or Subcontract (Legacy)
Add a Related Item to a Commitment Variation
Add Financial Markup to Commitment Variations
Add Payment application Contacts to a Purchase Order or Subcontract
Add Payment application Contacts to a Purchase Order or Subcontract (Legacy)
Allow Collaborators to Submit Site-initiated Variations
Approve and Sign a Subcontract	N/A	N/A	N/A	N/A
Change the Privacy Settings for a Commitment		+	+
Complete a Commitment Contract with DocuSign®  2
Complete a Commitment Variation with DocuSign® 2,8
Configure Settings: Commitments
Configure the Default Privacy Settings for New Commitments
Configure the Number of Commitment Variation Tiers
Create a Variation Request for a Commitment
Create a Commitment Variation
Create a Commitment Potential Variation from a Change Event 9
Create a Purchase Order		+	+
Create a Subcontract		+	+
Create a Subcontractor Payment application for the Release of Retention 1
Create a Payment Application on Behalf of a Payment Application Contact (Legacy) 3
Create a Payment Application on Behalf of a Payment Application Contact 3
Delete a Purchase Order or Subcontract
Delete a Commitment Synced with an Integrated ERP System 4
Delete a Subcontractor Payment application  10
Edit a Purchase Order (Legacy) 7		+	+
Edit a Subcontract (Legacy) 7		+	+
Edit a Commitment Synced with an Integrated ERP System		+	+
Edit the Advanced Settings Tab on a Commitment
Email a Commitment
Enable Financial Markup on a Commitment
Enable or Disable the Subcontractor BOQ Tab on a Commitment
Enable or Disable the Subcontractor BOQ Tab on the Commitments Tool
Enable the Payments Issued Tab on a Commitment
Enable Retention on a Commitment		+	+
Enable Sliding Scale Retention Rules on a Commitment's Payment Applications
Enable the Payments Issued Tab on a Commitment
Export a Commitment Variation to an Integrated ERP System
Export a Commitment to an Integrated ERP System
Export a Commitment 5
Export a Commitments List 7
Export a Payment Programme
Import Commitment BOQ Line Items from a CSV File		+	+
Request to Reset a Commitment Synced with an Integrated ERP System
Review a Subcontractor BOQ for a Commitment
Review Payment applications as a Subcontractor 1
Review Subcontractor Payment Applications as an Admin
Retrieve a Commitment from ERP
Search for and Apply Filters to Commitments
Send a Commitment Variation to ERP Integrations for Accounting Acceptance
Send a Commitment to ERP Integrations for Accounting Acceptance
Set or Release Retention on a Subcontractor Payment application 3
Submit a Site-initiated Variation as a Collaborator		+	+
Submit a New Payment application as a Payment Application Contact 3
Update a Subcontractor Bill of Quantities as a Payment Application Contact from the Payment applications Tool  1, 6
View a Purchase Order 7		+	+
View a Subcontract 7		+	+
View Inclusions/Exclusions for Subcontracts		+	+
View the Change History of a Commitment

¹ To perform this task, downstream collaborators should be designated as a payment application contact on the commitment. See Add Payment application Contacts to a Commitment. 

² Also requires a DocuSign^© account.

³  Users must have 'Read-Only' or 'Standard' permissions on the project's Commitments tool. Users must also be added to the Private drop-down list for that commitment or must be designated as a Payment Application Contact. See Add Payment application Contacts to a Purchase Order or Subcontract. 

⁴ 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®.  

⁵ Users with 'Admin' permissions on the project's Commitments tool can export a commitment as either a PDF or a DOCX file. Users with 'Standard' or 'Read-Only' permissions on the project's Commitments tool can export a commitment to the PDF file format if they have been granted access to the purchase order or subcontract via the Private drop-down list and the 'Allow These Users to See BOQ Items' tickbox is enabled.

⁶ 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.

⁷ 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. 

⁸ Also requires 'Standard' or 'Admin' permission on the project's Change Events tool.

⁹ 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.

¹⁰ The payment application must be in the 'Draft' or 'Revise and Resubmit' status for a user with 'Standard' level permissions to delete it.