Every integration is optional, is set up by your own people, and can be disconnected at any time. Each page lists the exact permissions requested and exactly which fields we read, and which we never do.
Last verified against our product: October 4, 2026
Principles that apply to every integration
Read-only. No integration writes to your HR, directory or calendar system.
Directory sources never request pay, government identifiers, date of birth or home address.
Calendar connections never request event titles, descriptions, locations or call links.
Connections are stored per organization behind database-level tenant isolation and are never returned by our API.
Disconnecting removes our stored connection. Also revoke the grant on the vendor side. See each page for what remains.
Directories and HR systems
Read-only imports of names, titles, departments and reporting lines. None of them write back.
BambooHRAvailable in the admin console Read-only employee directory sync from BambooHR through a one-click OAuth connection.
Gusto (payroll and HR)Connect flow built; availability depends on Gusto app approval Read-only employee directory sync from Gusto payroll through an OAuth connection.
HiBobConnect flow built; availability depends on HiBob app approval Read-only employee directory sync from HiBob through an OAuth connection.
JustworksConnect flow built; availability depends on Justworks app approval Read-only member directory sync from Justworks through an OAuth connection.
RipplingConnect flow built; availability depends on Rippling app approval Read-only worker directory sync from Rippling, started from Rippling's own app screen.
WorkdayNot self-serve yet Read-only worker directory sync from Workday using credentials your Workday admin generates (REST, v1).
Google Workspace directoryAvailable in the admin console Read-only user directory sync from Google Workspace through an OAuth connection by one admin.
Microsoft 365 / Entra ID directoryAvailable in the admin console Read-only user directory sync from Microsoft Entra ID through an admin-consented OAuth connection.
Calendar and messaging
Meeting-prep prompts and notifications in the tools your people already use.
SlackAvailable in the admin console Weekly prompts and new-intro posts to a channel you choose, plus an optional directory and direct-message grant.
Google CalendarAvailable to every member Read-only meeting times and attendee emails so Mucho Gusto can prompt you to watch an intro before you meet someone new.
Microsoft CalendarAvailable to every member Read-only meeting times and attendee emails from Outlook calendars, connected by each member.
Microsoft TeamsChannel notifications available; bot direct messages ship dark and are being verified with a first partner organization Weekly prompts and new-intro cards in a Teams channel through a webhook URL your admin creates, and, once enabled for your organization, private Teams messages from the Mucho Gusto bot.
Sign-in and provisioning
How people authenticate and how your identity provider manages accounts.
Sign-in and MFA (Clerk)Always on How people sign in, how MFA is enforced, and how verified email domains place new hires in the right organization.
SCIM provisioningScale plan and above Standards-based SCIM 2.0 user provisioning so your identity provider can invite and deprovision people.
Other directories
If your HR system is not listed, there are two routes. A directory in Google Workspace or Microsoft 365 / Entra ID can be connected with one click and gives us names, titles and reporting lines. A SCIM-capable identity provider can provision and deprovision people through SCIM. Those sources do not carry hire or termination dates, so tenure-based Belonging metrics need an HRIS connection.