General topics
Technical User
Understand the benefits, setup process, and governance of using a Procore Service Account for bulk actions.
In Construction Admin Helper, you have the choice between performing actions using your own Procore identity or using a Technical User (Service Account). This page explains how this optional feature works and how to set it up.
- 1 - What is the Technical User?
- 2 - Pros and Cons
- 3 - Installation Steps
- 4 - Permissions and Security
- 5 - How to Use it in the App
1 - What is the Technical User?
The Technical User is a Procore Service Account specifically tied to your Procore Company instance. When activated, it acts as a “robot” that executes bulk imports or updates on your behalf.
Such technical user is optional. We recommend starting without it and only implementing it once your governance and bulk-action needs are well-defined.
2 - Pros and Cons
Using a Service Account changes how actions are recorded in Procore’s change history.
| Feature | Using Your Own Account | Using the Technical User |
|---|---|---|
| Track Changes | Your name appears for every line modified. | The Service Account name appears. |
| Notifications | You may receive notifications as the “creator/editor”. | You are shielded from these notifications. |
| Rate Limiting | Shared limit of 3,600 calls/hour across all Procore companies. | Dedicated limit of 3,600 calls/hour per Company for this user. |
| Accountability | Very clear: you are the author. | Diluted: you cannot easily see which admin triggered the “robot”. |
[WARNING] Because the Service Account hides the identity of the specific person triggering the action, it requires strict internal governance, especially if multiple admins use the app.
3 - Installation Steps
To activate this account, you must be a Company Administrator in Procore.
- Request a Code: Contact support@constructionadminhelper.com to obtain your specific App activation code.
- Install the App: In Procore, go to App Management > Install App and enter the provided code.
- Identify the User: Once installed, a new user is automatically created in your Company Directory with an email format like
admin-actions-xxxxxxxx@procore.com. - Customize the Name: We strongly recommend manually editing this user in the Directory.
- First Name:
[Technical Account] - Last Name:
ADMIN HELPER - This ensures that the Change History in Procore remains clear for everyone.
- First Name:
4 - Permissions and Security
The Technical User is a “shell” with no permission by default. It can only act on tools and projects where you explicitly grant it rights, just like a human user.
Best Practices for Rights
- You should not grant “Company Admin” rights to the Technical User (for security reasons).
- Create a dedicated Permission Template (e.g., “[TECHNICAL] Service Account”) and assign it to the projects the user needs to work on.
Example: If the Service Account is an Admin on “Submittals” in Project A, but not in Project B, it will only be able to perform bulk actions on Submittals on Project A, and will not be able to perform bulik actions on Inspections on any project.
5 - How to Use it in the App
[IMPORTANT] you cannot log in as the Technical User. You always log in as yourself to manage exports and browse data.
The Service Account only intervenes during Bulk Imports:
- Go to an Import tool (e.g., Mass Import Inspections).
- Locate the checkbox:
Import via User API. - By default, this checkbox is unchecked (i.e. actions are done in your name). You can only check it if the Technical User has the required Admin permissions for that specific tool and project
- If you check it, the import is executed by the Technical User.
[SECURTY NOTE]: The Service Account credentials are encrypted, never shared with users, and are automatically rotated every 6 months to ensure maximum platform security.