Search
Clear search
Close search
Google apps
Main menu

Manage Chrome devices on multiple domains

If your organization owns more than one domain, you may want to configure Chrome settings across multiple domains. There is more than one way to accomplish this, but we recommend that you set up multiple domain management to manage Chrome devices across multiple domains.

Manage multiple domains from one Admin console (recommended)

After you choose to use one domain as your primary domain, you can still add secondary domains. After each domain is verified, you are free to create usernames and nicknames under it. All users within your account can then be managed under Users, created within the account. As long as your Chrome Device is enrolled to the primary domain, users on all domains in the account can have the same experience.

The advantage to this method is you can configure all settings on the same Admin console, and your users will all belong to the same account. This means that when you configure settings in Device management > Chrome management, you can have settings apply to users on different domains at once.

Device policies will apply to your enrolled devices regardless of the username. User policies, on the other hand, will affect users in your domain whenever they sign in to a Chrome device, even if the device isn’t enrolled to your account. You can set user and device policies for each of your organizational units, and each unit can contain devices and users from different domains within your account.

Please note these limitations to managing multiple domains.

Manage each domain using a different Admin console (not recommended)

Another approach you can take is creating separate accounts for each of your domains. This means that each of your domain act as a primary domain with its own Admin console, and you won’t run into any of the limitations that come with secondary domains. For most customers, we recommend against this approach because it comes with the following limitations:

  1. You will need to enroll devices separately for each Admin console. Rather than associating a Chrome device to your organization, it will belong to a subset of domains only. This means to make one change you must sign in to each Admin console.

  2. If you use G Suite, sharing between your domains will be more difficult. For many G Suite applications, there are settings limiting sharing permissions within the organization. With multiple accounts, you will be using two separate organizations.

  3. All management options will need to be handled separately. In addition to checking which organizational units should receive a certain setting, you now also need to check across your multiple Admin consoles.

The only main advantage to this approach is that you can easily set user policies by domain. Because the users are already separated by their domain, if you choose to have different user policies for each domain, it will be easy for you to configure. You won’t need to set up organizational units.

Changing Domains

If you purchased Chrome licenses for the wrong domain, please contact support.

Resources

Was this article helpful?
How can we improve it?