Configure Service Account Permissions
All Traditional Service Accounts will sunset on March 18, 2025.
Traditional Service Accounts were deprecated on December 9, 2021. Beginning January 21, 2025, we will no longer allow the creation of new Traditional Service Accounts. Existing Traditional Service Accounts will continue to function until March 18, 2025.
In accordance with this timeline, developers of data connection applications that currently use Traditional Service Accounts are required to update their applications to use Developer Managed Service Accounts, and customers will be required to install these updated applications before the sunset date. All data connection applications not migrated by the sunset date will cease to function. Any application listed on the Procore App Marketplace that is not using a supported method for accessing the Procore API will be removed by the sunset date. See Migrating Data Connection Applications to Use DMSAs for additional information.
Background
When you initially create a service account, default permissions are set to 'None' for all company level tools. You must set proper permissions for the service account prior to using it to access the Procore API. In addition, you can further refine and customize these permissions in order to implement and enforce more stringent security policies.
Important
Bear in mind that although you may be able to generate an OAuth 2.0 access token using a service account with default ('None') permissions, this token will not work for making successful calls to the Procore API. Therefore, you must set proper permissions for the service account prior to using it to access the Procore API.