Autodesk

The Corma and Autodesk integration keeps your Autodesk subscriptions, from AutoCAD and Revit to Fusion, assigned to the designers and engineers who use them. Autodesk says its technology spans architecture, engineering and construction, product design and manufacturing, and media and entertainment. Seats are assigned to named users in Autodesk Account, so a seat left with a former employee is a subscription nobody uses.

Key takeaways

• Autodesk admins assign each user a product seat from the team's pool of subscriptions or from one specific subscription ID.
• Autodesk named users sign in with their Autodesk ID, or their company ID when SSO is enabled, with one active session at a time.
• Autodesk user management has four admin roles: Primary admin (one per team), Contract manager / Purchaser, Secondary admin and SSO admin.
• Autodesk directory sync supports SCIM from Azure AD and Okta only, and comes with the Business Success Plan, which requires at least 50 subscriptions of eligible products.

What happens to Autodesk access when someone leaves?

An SSO login does not close the account. Autodesk's SSO FAQ explains that when a user leaves the company, their Autodesk account still exists and stays visible in User Management, and that administrators should remove unused accounts from licenses and product access. Removing a user from the team revokes product access and access to hub project data, but does not delete their personal Autodesk account.

When a Fusion hub admin has left, Autodesk's documented route to reassign hub admin rights needs the Autodesk Account credentials of both the former and the new hub admin, including access to the former employee's mailbox. Autodesk's usage report shows seat assignments and each user's last accessed date for single-user products, and the activity log keeps team events for at most one year, without export.

How Corma governs Autodesk

• Subscriptions in the budget: Autodesk subscriptions and their renewal dates sit in SaaS subscription management, so seats still assigned to people who left can be unassigned before renewal, as part of license reclaim.
• Leavers with a hub check: a leaver workflow in the IT Workflow Builder first asks an admin to reassign any Fusion hub admin rights while the person's mailbox is still reachable, then to remove them from the team.
• Admin roles under review: Primary, Secondary and SSO admins, and external users such as contractors, go into automated access reviews.
• Reporting tokens with an owner: the tokens obtained with a Business Success Plan Reporting API personal access token are bound to the user who created it, so each one is a non-human identity that needs a named owner.

Frequently asked questions

Does Autodesk support SSO and SCIM?

Yes. Autodesk's SSO guide says SSO is available to all Autodesk customers, set up at the domain level and based on SAML, and just-in-time provisioning can add users at their first SSO sign-in. SCIM comes through directory sync, which supports Azure AD and Okta only and requires the Business Success Plan. Read how SCIM and SAML differ.

How does Corma connect to Autodesk?

Autodesk documents no public API outside directory sync to add or remove users, so Corma's browser-based agents handle user steps in Autodesk Account, in an isolated browser session with credentials taken from your password vault. See also how Corma covers Autodesk Construction Cloud and BIM 360.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to know which Autodesk seats still sit with people who left? Book a Corma demo.