Updating the domain or adding a secondary domain to an Ashby account
If your organization has recently changed domain, or has a secondary domain, please reach out to [email protected] to update the domains on your Ashby account accordingly.
Updating your domain on your Ashby account
Please be sure to confirm the following before reaching out to Support to update your domain:
- Your systems admin has changed your company's primary domain in either Google Workspace or Microsoft 365, along with the primary domain in your identity provider if you are using SSO and/or SCIM with Ashby.
- Employees are actively using their email addresses with the new domain.
Support will confirm the above with you, along with the following before any updates are made:
- Whether all user email addresses should be updated to use the new domain in their profiles in Ashby.
- Whether you use auto-sync for your identity provider (if you have SCIM in place for signing in to Ashby). If so, users will sync as soon as the domain change has been made on Ashby’s side. This sync will remove any users not in your directory and add any directory users who are not already in Ashby. Please confirm you are ready for users to sync.
- In addition to making your new domain your primary domain, whether you would like your previous domain to be added as a secondary domain.
- Whether the new domain in the existing workspace or a separate workspace.
Please note: If this is a new domain for a separate Google Workspace instance and you’d like to set up domain-wide delegation for your other workspace, you will need to go through the scope setup process within the Google console of your separate instance. More on this here.
Adding a secondary domain to your Ashby account
Support will confirm with you as to whether this secondary domain is part of the same workspace or a separate one prior to adding the secondary domain.
Your domain is a secondary domain within the same Google Workspace instance or Microsoft tenant
In the case where the secondary domain is in the same Google Workspace instance, then Support will add the secondary domain to your account and no further action will need to be taken on your side.
Your domain is a domain within a separate Google Workspace instance
If this is a new domain for a separate Google Workspace instance and you’d like to set up domain-wide delegation for your other workspace, you will need to go through the scope setup process within the Google console of your separate instance.
If you already see the Ashby client ID listed in Security > API Controls > Domain-wide Delegation within your separate Workspace instance, then no further action is needed on your part. If the Ashby client ID is not listed in Domain-wide Delegation, then follow the steps at Google Workspace: Domain-wide Delegation, using the same client ID and authorizing the same scopes set for your primary domain to configure the integration in the same way for your second domain.
If the secondary domain is part of a separate instance, then users in the secondary workspace will not sync over to Ashby automatically and will need to have accounts provisioned for them manually. More on this at How do I provision new users in my Ashby account manually?How do I provision new users in my Ashby account manually? Email and calendar sync will only work after the user logs in to Ashby using their Google account.
Your domain is a domain within a separate Microsoft 365 tenant
If you are adding a new domain for a separate Microsoft 365 tenant, then users in the separate tenant would need to go through the individual OAuth process. Application-wide authorization can only be set up for one tenant. More on the Microsoft 365 integration process at Microsoft 365.
Users will not sync over to Ashby automatically if they are part of the secondary tenant, so would also need to be added manually via the steps at How do I provision new users in my Ashby account manually?
Email and calendar sync will also only work after the user logs in to Ashby using their Microsoft account.