This article addresses all the limitations associated with addition of secondary domains to a Google Apps account. The following features differentiate what is supported for primary and secondary domains.
- You cannot set different policies or configuration settings for different domains. All settings in the Google Admin console apply equally to all domains that are part of your account.
- You can specify only one custom logo for your account. The same logo appears for users in all domains that are part of your account.
Domain names and aliases:
- Domain aliases are supported for the primary domain only. You cannot create a domain alias for a non-primary domain. If users in a non-primary domain need alternate email addresses like the ones created by a domain alias, you can use the Admin console or the Provisioning API to give each user an email alias at the target domain. For example, instead of defining alias.com as a domain alias for domain.com, you can add domain.com and alias.com to your account as separate domains, then create an email alias email@example.com for each firstname.lastname@example.org.
- Google Apps account merge is not supported. Some current Google Apps customers with multiple domains currently have separate Google Apps accounts for each domain. Google does not currently support merging multiple Google Apps accounts into a single multiple domain account.
- Migration from domain aliases is not supported. Some current Google Apps customers use domain aliases for their non-primary domains. Google does not currently support the conversion of domain aliases into multi-domain accounts.
Account Access URLs:
- Custom URLs for accessing Google Apps are available only for the primary domain. The Admin console enables the administrator to set a custom URL for various services. The custom URL applies only for users accessing the services at the primary domain. The same limitation applies to custom web address mapping for a Google Site.
- You cannot create a global URL for accessing Google Apps. Users access Google Apps with a URL that includes the domain name from their email address, for example http://docs.google.com/a/subsidiaryA.com. You cannot provide a global URL that users from all domains share.
- Email and contact delegation does not work across domains. A user cannot grant access to a user from a different domain. A workaround for this limitation is to create an email alias for the user in the same domain as the user to whom you want to grant access.
- You cannot share Google Drive files across domains using "Get the link to share". A user can share a Google Drive file with a user in another domain by clicking Share and inviting the user. However, when a user selects Get the link to share, recipients at other domains cannot use the generated link to access the document.
- You cannot restrict sharing to the users in a single domain. Sharing options are based on the organization as a whole, not individual domains. To share a document with the users in a single domain (or any other subset of users), create a Google Group that includes all the users and share the document with that group.
- When you share a site with a user from a different domain, the user sees a login screen for your domain. To access the site, the user needs to click Sign in with a different account before entering his or her account information. (Limitation only for legacy Google Apps accounts that have not transitioned to the new infrastructure)
- You can only create a custom web address mapping for a site at the primary domain.
- Searches for sites only return sites in the same domain as the user. For example, a user with an address in a secondary domain will not find sites created in the primary domain.
- Applications that use Google App Engine are not available for users at non-primary domains.
Postini for Google Apps:
- Existing Google Apps domains that use the Postini for Google Apps service are unable to add secondary domains.