Frequently Asked Questions
This page collects answers to common questions about working with Secure Service Accounts (SSAs) in production. For the recommended Robot-per-Tenant pattern for ISVs, see Tenant Isolation for ISV Integrations. For broader production guidance, see Best Practices. For current limitations and behavioural gotchas, see Known Issues.
In this page, robot is informal shorthand for a Secure Service Account (SSA) — the non-human identity your app creates through the SSA API. Each SSA has its own email address, appears as a member in Forma Hub and Project admin interfaces, and is used to obtain three-legged access tokens for API calls. See API Basics for the full lifecycle.
Is there a limit on Service Accounts per Client ID?
The default limit is 10 Service Accounts per Client ID. For ISVs requiring more than 10 tenants in production, submit a request through Get Help on the APS portal to request an increase. You must have an active Autodesk Developer Network (ADN) membership to use Get Help.
See the SSA account limit entry in Known Issues for what to include in your request.
Can a customer’s admin see or manage their robot?
Yes. The robot appears as a regular member in their Forma Hub and Project admin interfaces. The customer admin can:
- View the robot’s permissions.
- Remove the robot from projects (which disables your integration for that scope).
- Audit the robot’s activity through Forma audit logs.
This is by design — the customer retains full control over what the robot can access, and full visibility into what it has done.
How can we automate adding the robot to new projects?
The recommended approach is project templates. If you create projects from a template that already includes the SSA with the appropriate role (for example, Project Admin or a custom role), the service account is provisioned with access automatically when the project is created.
Additional Information (not specifically about SSA):
To detect when a new project has been created so that you can trigger downstream automation:
- Polling (recommended, supported): Use the Account Admin Projects API with
filter[updatedAt]and track previously-unseen projectidvalues. This is the reliable, supported approach today. - Cost webhook (limited): If your customers use Forma Cost, you can subscribe to
project.initialized-1.0from theautodesk.construction.costevent system at account scope. This fires only for Cost-enabled projects.
Do not use dm.folder.added on an “account root folder” to detect new projects. This was a workaround mentioned in older guidance but is not viable for general use: there is no public account root folder ID that contains projects as subfolders. That approach relied on an internal employee permission not available to third-party developers.