Permissions

ERP Integrations: QuickBooks

The following table highlights which user permissions are required on the ERP Integrations tool to perform the described user action.

This page details the Procore tools and minimum permissions required to complete specific tasks when your company's Procore account has the ERP Integrations tool configured to work with QuickBooks. 

Admin
Task	Standard	Admin	Procore point of contact
Configure Cost Code Preferences for QuickBooks
Send Unsynced Standard QuickBooks Cost Codes to ERP Integrations for Accounting Acceptance
Delete Project Cost Codes from a Procore + QuickBooks® Project
Bidding
Task	Standard	Admin	Procore point of contact
Award a Winning Bid and Convert it to a Purchase Order
Award a Winning Bid and Convert it to a Subcontract
Budget
Task	Standard	Admin	Procore point of contact
Create a Budget Line Item
Create a Missing Budget Line Item
Create a Budget Modification
Lock a Budget
Resend a Rejected Budget to ERP Integrations for Accounting Acceptance
Retrieve a Budget from ERP Integrations Before Acceptance
Send a Budget to ERP Integrations for Accounting Acceptance
Commitments
Task	Standard	Admin	Procore point of contact
Create a Commitment	2
Create a Commitment Change Order (CCO)
Create a Purchase Order	2
Create a Subcontract	2
Delete a Commitment Synced with QuickBooks
Edit a Commitment (Unsynced)	3
Edit a Commitment Synced with QuickBooks	3
Request to Delete a Commitment Synced with QuickBooks
Resend a Rejected Commitment to ERP Integrations for Accounting Acceptance
Resend a Rejected CCO to ERP for Accounting Acceptance
Retrieve a Commitment from ERP Integrations Before Acceptance
Retrieve a CCO from ERP Integrations Before Acceptance
Send a Commitment to ERP Integrations for Accounting Acceptance
Send a CCO to ERP Integrations for Accounting Acceptance
Directory
Task	Standard	Admin
Add a Company to the Company Directory
Add a Company to the Project Directory	5
Consolidate and Link QuickBooks Vendors to Procore Companies
Create and Sync Vendors with the QuickBooks Integration		4
Link a QuickBooks Vendor to a Procore Company
Retrieve a Company from ERP Integrations Before Acceptance		4
Resend a Rejected Company to ERP Integrations for Accounting Acceptance
Send a Procore Company to ERP Integrations for Accounting Acceptance
Portfolio
Task	Standard	Admin	Procore point of contact
Add a New Procore Project into QuickBooks	7
Reports
Task	Standard	Admin	Procore point of contact
View a QuickBooks Job Cost Report	6
ERP Integrations
Task	Standard	Admin	+ Accounting Approver
Accept or Reject a Budget for Export to QuickBooks
Accept or Reject a Commitment for Export to QuickBooks
Accept or Reject a CCO for Export to QuickBooks
Accept or Reject a Procore Company for Export to QuickBooks
Export a Budget to QuickBooks
Export a Commitment to QuickBooks
Export a CCO to QuickBooks
Export a Vendor/Company to QuickBooks
Unlink CCOs Synced with QuickBooks®		8

¹ Also requires the 'Can Push to Accounting' privilege. 

² Also requires the 'Create Purchase Order' and/or 'Create Subcontract' granular permission. For special use cases, Read-Only users can also be granted granular permission to perform these tasks. See Grant Granular Permissions in a Project Permissions Template.

³ Also requires the 'Update Purchase Order' and/or 'Update Subcontract' granular permission. For special use cases, Read-Only users can also be granted granular permission to perform these tasks. See Grant Granular Permissions in a Project Permissions Template.

⁴ Also requires the 'Admin' level permission on the ERP Integrations tool.

⁵ Also requires the 'Create and Edit Companies' granular permission. For special use cases, Read-Only users can also be granted granular permission to perform this task. See Grant Granular Permissions in a Project Permissions Template.

⁶ The Project level report also requires 'Read-only' level permission on the Budget and Prime Contract tool. The Company level report does NOT support 'Standard' level permission access. 

⁷ Also requires the 'Add New Project' privilege. See Allow Users to Create New Projects. 

⁸ Also requires 'Admin' level permission on the Commitments tool. 

Job Role

The following table highlights which user permissions are typically granted to a user based on their job role on a project. A user's permissions for a specific tool are granted on a per project basis. To learn how to create permission templates that you can apply to groups of users based on their job role, see Create User Permission Templates.

Job Role	None	Read Only	Standard	Admin
Accountant
Architect
Company Administrator
Engineer
Owner / Construction Manager
Project Manager
Subcontractor
Superintendent