Integrations
Platform
Does Ashby support integrating with multiple instances of Google Workspace or Microsoft 365?
4 min
ashby does support connecting multiple instances (domains or tenants) of google workspace or microsoft 365 within a single ashby account however, these instances are treated independently and do not behave as a unified system 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 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? regardless of the integration setup, users from any domain or tenant can log in and access ashby (if provisioned) leave interview feedback submit referrals review applications collaborate on candidate profiles and leave notes create jobs and reports subject to access permissions — see docid\ i5jhibmkqhyobnnvrl8rk for more what are the limitations? when users from different platforms or domains try to interact through ashby, they’ll run into these constraints can’t schedule interviews for users outside their own domain or tenant can’t send emails on behalf of users from other domains or tenants calendar availability is only visible within the same domain/tenant conferencing links cannot be embedded across platforms these limitations are imposed by the native behaviors of google and microsoft apis, which ashby respects to maintain security and stability will ashby support unified cross domain or cross platform scheduling in the future? it’s unlikely these limitations stem from how the underlying platforms work — ashby reflects those constraints to avoid introducing data access issues or unreliable functionality if your organization operates across multiple domains or tenants, we recommend choosing a primary domain for recruiting or working with your it team to centralize recruiting related calendars and emails under a shared instance let me know if you'd like this reformatted for an internal faq, help center article, or admin training doc