Single sign-on (SSO)

Someone leaves. IT disables their Google account, then works down a list of other tools from memory, and whatever isn’t on that list keeps working. The bigger your team, the longer that list and the easier it is to miss a line. As part of the Got Your Back release, we’re taking a closer look at single sign-on, which takes Herodesk off the list entirely.

Sign in with the identity you already have

Connect Herodesk to Google Workspace or Microsoft 365 over OAuth, and your team signs in with the corporate credentials they already use instead of a separate Herodesk password. Whatever your identity provider enforces (MFA, device rules, session limits) now covers Herodesk too, without configuring any of it twice.

Offboard in one place

Because access flows from your identity provider, disabling someone there takes their Herodesk access with it. There’s no separate account left behind to remember, and no window where a leaver can still open the customer base. For a larger B2B or SaaS team already running an IdP, that’s the whole point.

Exemptions, on the record

Some accounts don’t fit: a contractor, a shared login, an edge case. You can grant per-user SSO exemptions, temporary or permanent, and every one of them is written to the audit log, so nothing is quietly excepted. SSO sits alongside two-factor authentication and the admin, manager and agent roles rather than replacing them.

Where to find it

Single sign-on is configured in admin settings, where you connect your identity provider and manage exemptions. It’s part of the autumn Got Your Back release. Single sign-on is available on Herodesk Pro. Read more on the Single sign-on feature page.