Autodesk User Management Guide

• Model type: role-based
• Description: Autodesk Account uses a fixed set of administrative roles (primary admin, secondary admin, SSO admin, contract manager/purchaser) to control who can manage users and product assignments. Product access for end users is controlled by seat assignment (named-user subscription or Flex token). Within Autodesk Construction Cloud (ACC), account administrators can create custom named roles (e.g., Submittal Manager, Project Administrator) that control tool-level access within projects. These ACC roles are separate from the Autodesk Account admin roles.
• Custom roles: Yes
• Custom roles plan: Custom roles within Autodesk Construction Cloud (ACC) are available to ACC account administrators. Autodesk Account admin roles (primary, secondary, SSO) are fixed and not customizable.
• Granularity: At the Autodesk Account level: coarse-grained fixed roles controlling user management and billing. At the ACC/BIM 360 level: fine-grained custom roles controlling tool and project access. Product-level service customization (assign/unassign individual cloud services within a product) is available to primary, secondary, and SSO admins.

1. Sign in to Autodesk Account at manage.autodesk.com.
2. Navigate to User Management > By User.
3. Select the team to which you want to add users (if multiple teams exist).
4. Click 'Invite Users'.
5. For individual invite: enter the user's first name, last name, and email address, then click 'Send Invite'.
6. For bulk import: select the 'Import' tab, click 'Upload CSV file', select your prepared CSV file, and click 'Continue' after upload completes.
7. After users are added to the team, assign product seats via User Management > By Product or By User.

Required fields: First name, Last name, Email address

Watch out for:

• Adding a user to the team does not automatically assign product access; product assignment is a separate step.
• Invited users have 7 days to accept the invitation via the emailed link before the invite expires and must be resent.
• If the invite is not accepted within 90 days, the user must be re-added entirely.
• Users without an existing Autodesk account will appear as 'Invited'; users with an existing account appear as 'Verified'.
• Users assigned via CSV bulk import do not receive an email notification of the product assignment.
• Users added via directory sync cannot be manually removed from the team through the admin console; they must be removed from the IdP directory.
• Nested groups are not supported in directory sync.
• JIT provisioning creates the account automatically on first SSO sign-in but does not auto-assign products; product assignment must still be done manually or via group assignment.

• Can delete users: Verify in tenant
• Delete/deactivate behavior: This app exposes delete operations in its API documentation, but the admin-console path may present removal as deactivation, archiving, or deletion depending on tenant configuration. Confirm whether the UI action is reversible before treating removal as recoverable.

1. Sign in to manage.autodesk.com.
2. Navigate to User Management > By User.
3. To remove a single user: select the user, then click the remove user icon (trash can icon next to the user's name), and confirm by clicking 'Remove' in the confirmation dialog.
4. To remove multiple users in bulk: select the checkboxes next to one or more users, click 'Remove users' at the top right, and confirm by clicking 'Remove'.
5. For users added via directory sync: remove the user from the relevant group in your IdP (Azure AD / Okta); the removal will sync to Autodesk Account.

Watch out for:

• Primary admins cannot be removed from the team unless their admin role is first reassigned to another secondary admin.
• Users added via directory sync cannot be removed manually through the Autodesk admin console; they must be removed from the IdP directory.
• Removing a user from the Autodesk Account team does not delete their personal Autodesk account.
• Hub admins for ACC and BIM 360 should be notified before a user is removed, as the user will lose access to linked hubs and projects immediately.
• For some collaboration products, additional manual steps are required to fully revoke access to collaboration sites even after team removal.
• When using SSO, a removed user's active session on a device will continue until the session expires.

• Where to check usage: manage.autodesk.com > Reporting > Usage Report (direct URL: https://manage.autodesk.com/usage-report-v2). Filter by team, date range, product, user activity (active/inactive), and seat assignment status. Export available in CSV format. Scheduled recurring exports can be configured (up to 5 scheduled reports per admin).
• How to identify unused seats: In the Usage Report, filter by 'Inactive' user activity status to identify users who have not accessed a product within the selected date range. The report shows last accessed date, days used, and assignment date. Admins can export the report and analyze in Excel. Note: offline usage is not captured in the Usage Report.
• Billing notes: Subscriptions are managed under Billing and Orders > Subscriptions and Contracts in Autodesk Account. Seats can be assigned from a shared pool (system auto-selects subscription) or pinned to a specific subscription ID. If a user is pinned to a specific subscription ID and that subscription expires, the user loses access even if other seats are available in the pool. Annual and 3-year multi-user subscriptions do not auto-renew; the license file must be updated manually. The contract manager/purchaser role manages renewals and billing; this role is separate from the primary admin role unless held by the same person.

Every app requires a named-user seat assignment after the invite is accepted, and invites expire after 7 days-meaning a missed follow-up forces a resend cycle before any work can start.

Directory sync (SCIM) is gated behind the Business Success Plan, an additional subscription on top of product costs; without it, every joiner, mover, and leaver is a manual console operation. The Usage Report filters inactive users but excludes offline activity, so identifying truly unused seats across every app requires manual cross-referencing and judgment calls.

The most consistent friction point reported by admins is the Business Success Plan requirement for SCIM-it adds meaningful cost and is a hard blocker for smaller teams that want automated provisioning. SSO enforcement is domain-wide with no per-user opt-out, which creates complications during phased rollouts.

JIT provisioning via SSO creates accounts automatically but does not assign product licenses, leaving a gap that still requires manual intervention or group-based assignment configuration.

Common complaints:

• Directory sync (SCIM) requires the Business Success Plan (previously called Premium plan), which is an additional subscription cost on top of product subscriptions; this is a significant barrier for smaller organizations and education institutions.
• SSO is configured at the domain level; once enabled, all users in the domain must authenticate via SSO, with no per-user opt-out.
• Users provisioned via directory sync cannot be manually removed from the Autodesk admin console; removal must be performed in the IdP, which can delay offboarding.
• JIT provisioning via SSO creates user accounts automatically but does not auto-assign product licenses; admins must still manually assign products or configure group-based assignment.
• There is no granular RBAC for product assignment delegation; the only roles available are full admin roles, making it impossible to give teachers or team leads the ability to assign products to their own users without granting full admin access.
• The Usage Report does not capture offline product usage, making it difficult to accurately identify truly inactive users.
• CSV bulk import for user invitations can fail with non-descriptive error messages; an Autodesk-exported CSV file cannot be re-imported without reformatting.
• Removing a user from the Autodesk Account team does not automatically remove them from ACC or BIM 360 project sites; additional manual steps are required in each collaboration product.
• The contract manager/purchaser role can only be changed by opening a support case via the Autodesk Assistant, with no self-service option in the admin console.
• Licensing errors and seat assignment discrepancies are commonly reported, with users experiencing product shutdowns despite valid active subscriptions showing in the portal.

Manual management is workable for small, stable teams where every app's user list changes infrequently and the admin overhead is predictable.

It becomes a liability at scale: no bulk deactivation shortcut, no granular delegation (team leads can't assign their own users without full admin rights), and offboarding for SCIM-provisioned users must happen in the IdP-not the console.

Teams with high contractor turnover or frequent seat reallocation across every app will feel the compounding cost of these gaps quickly.

Bottom line

Autodesk's manual user management is functional but deliberately coarse: fixed admin roles, a two-step invite-then-assign workflow, and no delegation below the full-admin level. Every app in the portfolio follows the same model, so the operational burden scales linearly with headcount and product breadth.

The Usage Report gives visibility into inactive seats, but acting on that data-reassigning or removing users-remains a per-user console task unless SCIM is in place.