Before installing any Procore Marketplace app, it's reasonable to want to know exactly what it can access — without taking the vendor's word for it. This page shows how to confirm that TonicDM connects with User-Level Authentication and therefore can never do more than the individual user who connected it is already permitted to do.
What "User-Level Authentication" means
Procore documentation: https://v2.support.procore.com/faq-how-do-integrations-with-procore-access-my-companys-data
Procore apps access your data in one of two ways:
DMSA: Service-account apps act with their own standing identity. At install they ask you to grant a set of tool permissions, and they create a persistent service-account "user" in your Company Directory that can act across projects regardless of who is using the app.
Authorization Code: User-Level apps — like TonicDM — have no identity of their own. Each of your users connects individually through Procore's standard login-and-authorize flow, after which TonicDM can act only as that user, bounded by exactly the company- and project-level permissions you have already assigned them in Procore.
TonicDM uses the second model. Here is how to confirm it for yourself.
Verify it in Procore
Watch the install flow. A service-account app shows a modal listing specific tool permissions you must grant before installing. TonicDM's installation presents no such permissions grant — because there are no standing permissions to give.
This link shows what you see when installing a "service-account" app. You will not see this with TonicDM. https://v2.support.procore.com/product-manuals/admin-company/tutorials/Install-data-connection-appCheck your Company Directory. Service-account apps automatically create a new "user" account in Company Admin → Directory with its own permission template. Search the Directory after installing TonicDM: you will find no TonicDM account. The app has no identity to act as.
Check App Management. In Company Admin → App Management, open TonicDM. There is no service-account permission template for you to create or assign — a step that service-account apps require and user-level apps do not have.
How this works
Because every request TonicDM makes carries an individual user's token, Procore's API enforces that TonicDM can only see and do what that user can already see and do. Anything outside their project membership or permissions is refused by Procore. This boundary is held by Procore, not by us.
In practice: to control what TonicDM can access for any user, you manage it the same way you already manage that user, through their Procore permission templates and project assignments. Installing TonicDM does not change anyone's existing access.
Revoking access
You can uninstall TonicDM in Procore's App Management page.