<aside>
💡
Ashby only supports one full org-wide integration per Ashby org:
- One Google Workspace tenant or
- One Microsoft 365 tenant
That org-wide integration enables:
- Directory sync (via SSO/SCIM)
- Shared calendars/resources (e.g.,
[email protected])
- Org-wide email/calendar sync
</aside>
What about multiple domains or tenants?
- Multiple domains under one tenant (e.g.,
@acme.com and @subsidiary.acme.com) are supported and will work normally.
- Secondary tenants can only connect via Personal OAuth in Personal Settings. This works the same way external interviewers connect their accounts.
Limitations of OAuth for secondary tenants:
- No cross-tenant availability or scheduling visibility
- No shared calendars/resources across tenants
- No central provisioning (each user must be added manually)
<aside>
💡
Users across different domains or tenants will face the same platform-level limitations when trying to schedule interviews or send emails to one another through Ashby.
</aside>
What does that mean in practice?
You can configure more than one domain (e.g., @acme.com and @subsidiary.acme.com) or tenant, and users under each can connect their calendars and inboxes via Personal Settings.
However:
- Email and calendar features will only work within the same domain or tenant
- Users from one domain cannot schedule on behalf of or email as users from another
- Google Meet links can't be embedded in Microsoft Outlook events, and vice versa
- Free/busy availability can’t be shared between users on different platforms or domains
Ashby mirrors Google and Microsoft's native limitations. They don’t support seamless cross-domain scheduling or delegation unless complex enterprise trust relationships are configured, and even then, Ashby does not support those workarounds.
What can users still do across instances?