Account management for admins
Manage user role policy
Use user role policy to control whether people on your Autodesk account team are classified as users or external users. Learn how User-management based and Domain based policies work, why someone may be classified as an external user, and how user roles work with Subscription usage policy.

An external user is typically someone outside your organization, such as a contractor or vendor, who needs access to Autodesk products or services. External users were previously called guest users.
Your team can use either User-management based or Domain based user role policy. The policy determines how people are classified when they're added to your team.
The initial user role policy for a team depends on when the team was created. Teams created from October 2026 onward use Domain based user role policy by default, with the primary admin's email domain added as the first domain. Teams created before October 2026 aren't automatically changed and may continue to use their existing user role policy.
User role classification is also used by other Autodesk account controls, including Subscription usage policy. If your Subscription usage policy treats external users differently, make sure your users are classified according to your organization's requirements.
If this sounds like you… | Start here | This path is for… |
Someone from my company is showing as an external user. | Why someone may be classified as an external user | Understanding how the team's current policy classified the person. |
I want people from our company to be recognized automatically. | Use Domain based user role policy | Automatically classifying people as user instead of external user by approved email domain. |
We're restricting external users and I want to make sure the right people are affected. | Understand how user role policy works with Subscription usage policy | Reviewing role classification before applying subscription restrictions based on user role. |
This person's role doesn't match our domain rule. | Review user role policy exceptions | Reviewing people whose existing role differs from the role expected by the current domain policy. |
With User-management based user role policy, people added to your team through an integrated Autodesk cloud collaboration product, such as Forma Design Collaboration, Forma Build, or Forma Takeoff, are automatically set as an external user in your Autodesk account.
User-management based policy can be appropriate when your organization already has a reliable process for making sure people are correctly classified as users or external users.
With Domain based user role policy, you create a list of approved email domains for your team.
This lets you automatically manage who is considered a user or external user, regardless of whether they're added through Autodesk account or an integrated cloud collaboration product. Anyone added with an email from an approved domain will be assigned as a user, while users with emails from other domains will automatically be set as external users.
Domain based policy can be useful when people are frequently added through cloud collaboration products because it lets Autodesk classify them automatically based on their email domain.
For teams created from October 2026 onward, Domain based is the default user role policy. The primary admin's email domain is automatically added as the first domain.
Teams created before October 2026 aren't automatically changed. Their existing user role policy remains in place unless an admin changes it.
Selecting the domain based policy doesn't change the roles of existing users. The policy applies only to new users. To update existing users' roles, use the options in User management.
Note: Include your organization's domain for single sign-on (SSO) or directory sync in your domain based rules. This ensures that team members using SSO are automatically recognized as standard users.
How a person is classified depends on the user role policy for the team.
With User-management based policy, someone added through an integrated Autodesk cloud collaboration product can be classified as an external user even if they're an employee or otherwise part of your organization.
With Domain based policy, the person's email domain is used to determine their role. A person whose email domain matches an approved domain is classified as a user. A person whose domain doesn't match is classified as an external user.
Go to Settings > Team settings in your Autodesk account.
Select the appropriate team.
Review User management policies to see whether the team uses User-management based or Domain based policy.
If the team uses Domain based policy, check whether the person's email domain is included.
If the person was already on the team before the current Domain based policy applied to them, check View exceptions in Manage policies.
Note: If you need to review multiple exceptions, open View Exceptions and filter the list by Users or External users. You can export the filtered list and compare it with your internal records before deciding whether any roles need to change.
Changing someone's role classification doesn't change the organization they work for, their project role, or their product assignment.
User role policy and Subscription usage policy control different things.
Setting | What it controls |
User role policy | Whether someone is classified as a user or external user on the Autodesk account team. |
Subscription usage policy | Whether applicable subscriptions assigned by the team can be used on projects associated with another team. Some Subscription usage policy settings treat users and external users differently. |
When Subscription usage policy is set to Restricted for external users, a person's classification matters because the restriction applies to people classified as external users.
Before relying on this setting, review your team's user roles and make sure people are classified according to your organization's requirements.
This is especially important for people added through cloud collaboration products. With User-management based policy, those people can be classified as external users. Domain based policy can reduce unintended classification by automatically recognizing people whose email addresses match your organization's approved domains.
You do not have to change to Domain based policy solely because you use Subscription usage policy. If your organization already has another reliable process for keeping user and external user roles accurate, you can continue using that process.
For information about whether an applicable subscription can be used on another team's project, see Manage subscription usage for external Forma projects.
Use Domain based policy when you want to classify people automatically according to their email domain.
Go to Settings > Team settings in your Autodesk account.
Select the team you want to manage.
Under User management policies, select Manage policies.
Select Domain based.
Add the email domains that identify people who should be classified as users.
Select Apply Changes.
Confirm the policy update.

New people added to the team are classified according to the domain policy.
Primary, secondary, and single sign-on (SSO) admins aren't affected by the domain rule.
Note: Changing to Domain based policy doesn't automatically change the roles of people already on the team. People whose existing roles don't match the current domain policy appear as exceptions.
You can add multiple domains to your Domain based user role policy.
Add a domain when people using that email domain should normally be classified as users on the team.
Make sure you include all relevant organizational domains, including domains used with SSO or directory sync when applicable.
To add a domain:
Go to Settings > Team settings in your Autodesk account.
Select the appropriate team.
Under User management policies, select Manage policies.
Select Add domain to add as many domains as you need.
Select Apply Changes at the bottom of the screen.
Confirm your policy update.
New users whose email addresses match a listed domain are classified as users. New users with email addresses from other domains are classified as external users.
You can remove domains from a Domain based user role policy. At least one domain must remain.
To remove a domain:
Go to Settings > Team settings in your Autodesk account.
Select the appropriate team.
Under User management policies, select Manage policies.
Review the domains in the policy.
Select Remove for the domain you want to remove.
Select Remove to confirm the removal.
New users whose email addresses use the removed domain are classified as external users.
Existing users keep their current roles. If their roles no longer match the domain policy, they appear as exceptions.
An exception is a user whose current role doesn't match the role that the team's Domain based policy would assign.
For example, someone who was already on the team before their email domain was added to the policy keeps their existing role. If that role doesn't match the current domain rule, the person appears as an exception.
An exception isn't necessarily an error. It means the person's role differs from the role expected by the current domain policy. Review the person's relationship to your organization and, when needed, compare the exception with your internal records before deciding whether the role should change.
To review exceptions:
Go to Settings > Team settings in your Autodesk account.
Select the team you want to manage.
Under User management policies, select Manage policies.
Select View Exceptions in the Approved email domains section.
Compare each user's current role with the role expected by the domain policy.

You can filter the list to review All roles, Users, or External users.
Note: You can export the exceptions list after filtering by Users or External users. Compare the exported list with your internal systems to confirm which roles should change. After you validate the changes, use the By user page in User management to make role changes in bulk.
Reviewing exceptions is particularly important if your Subscription usage policy treats external users differently.
To change the role of a user listed as an exception:
Go to Settings > Team settings in your Autodesk account.
Select the appropriate team.
Under User management policies, select Manage policies.
Select View Exceptions in the Approved email domains section.
Select the user whose role you want to change. You can select multiple people.
Select Change roles.
Choose the appropriate role.
Select Change role to save your changes.
When you select multiple users, the same new role is applied to everyone selected.
You don't have to remove every exception. The team admin should decide which role is appropriate for each user based on the organization's requirements.

You may see an alert in a user's details when their current role doesn't match the Domain based policy.
Review the user's role and decide whether to keep the exception or change the role to match the domain rule.

When a user's current role doesn't match your Domain based user role policy, their role is an exception.
If you change the user's role to the role specified by your domain rule, you'll see a message letting you know that the user's current role is an exception.
If you want the user to follow your domain rules, select Undo exception. The user's role will then match the role determined by your Domain based policy.
If the user's current role is intentional, you can leave the exception in place.

You may see this message when changing the role of someone whose current role matches the Domain based policy.
Continue with the change if you intentionally want the person to have a different role from the one assigned by the domain rule.
You can review the person later from View exceptions.
If your question is about any of the following, see Manage subscription usage for external Forma projects instead:
Whether your organization provides the subscription for an external user.
Whether someone can use their assigned subscription on another team's project.
Why an external user can't use an applicable subscription on a project.
How Subscription usage policy treats users and external users.
Questions about user classification and questions about subscription usage are related, but they control different parts of the experience.
Frequently asked questions (FAQs)
Why was someone from my organization classified as an external user?
First check which user role policy the team uses.
With User-management based policy, people added through integrated Autodesk cloud collaboration products can be classified as external users.
With Domain based policy, classification is based on email domain. Make sure the person's organizational domain is included in the policy.
If the person was already on the team before the applicable domain rule, their existing role may remain and appear as an exception.
Do I need to use Domain based policy with Subscription usage policy?
No. What's important is that people are correctly classified as users or external users according to your organization's requirements.
Domain based policy provides an automated way to maintain those classifications using email domains. If your organization already has another reliable process for keeping roles accurate, you don't need to switch solely because you use Subscription usage policy.
Why does user role matter when Subscription usage policy is Restricted for external users?
The Restricted for external users setting applies its cross-team subscription restriction according to the person's role on your Autodesk account team.
If someone who should be treated as a user is classified as an external user, that person can be affected by the restriction.
Does changing someone's user role change their subscription?
User role policy classifies the person as a user or external user. It does not by itself assign or remove a product subscription.
For questions about using an applicable subscription on projects associated with another team, see Manage subscription usage for external Forma projects.
Does changing someone's user role change their project permissions?
User role policy applies to the person's Autodesk account team role. It doesn't change the role the person holds within a Forma project.
Why does another team have a different user role policy configuration?
The initial user role policy depends on when the team was created.
Teams created from October 2026 onward use Domain based user role policy by default, with the primary admin's email domain added as the first domain.
Teams created before October 2026 aren't automatically changed and may continue to use User-management based or another existing user role policy configuration.
This means teams in the same Autodesk account can have different user role policy configurations.
What happens to existing users when I set up Domain based policy?
Existing roles don't change automatically.
If an existing person's role doesn't match the role expected from their email domain, the person appears as an exception. Review the exception and decide whether their current role should remain or change.
How are user role policy domains related to SSO or directory sync domains?
When Domain based policy is active, users are classified according to the domains included in that policy.
If you want people added through SSO or directory sync to be classified as users, make sure the applicable organizational domain is included.
Example: If you turn on the domain based external user rule and only include domain cba.net, but your SSO or AD domain is abc.net, the system adds users synced through SSO or AD as external users in your user management.
What happened to guest users?
Guest users are now called external users. You don’t need to change how you work, only the name has changed.
Does user role policy affect default product assignments?
User role policy and product assignment are separate controls. Changing someone's classification doesn't by itself change their product assignment.
Can I see whether someone is an external user in usage reports?
Yes. Usage reports can identify people classified as external users.
How do I manage an exception?
Use View exceptions under Approved email domains or update the person's role from their user details.
Related resources
Need help? Ask the Autodesk Assistant!
The Assistant can help you find answers or contact an agent.
What level of support do you have?
Different subscription plans provide distinct categories of support. Find out the level of support for your plan.
View levels of support