Skip to content
A red and white streetcar on a downtown street lined with glass office towers.

Single sign-on: one less password for everyone who needs help

Every new password is a reason not to use the portal. Single sign-on lets customers and employees into your help center with a login they already have, so the portal gets used instead of emailed around.

Get started for freeWatch a demoNo credit card. No contract.

What single sign-on changes for staff and customers

With single sign-on, people reach the portal with a login they already have. A login screen is often the reason people email instead of using the help center, and SSO removes it. For an internal IT desk that means staff submit and track tickets through the portal with their Windows login, and "I couldn't get into the help desk" stops being a ticket of its own.

For a software company, it means customers who are already signed in to your product are signed in to support too. They see their ticket history and your help articles, with no second account to create or forget.

Three ways into the portal, and one for agents

The first is built in: Google and Facebook buttons on the portal login, with nothing to configure, on every plan. Good for consumer-facing support where customers have one of those anyway.

The second is Active Directory, for the internal help desk. Employees use the login they already have.

The third is your own application. Your app verifies the user, then sends them to the portal with their name, email, a timestamp and a hash signed with a secret Cayzu gives you. Cayzu checks the signature and lets them in. This is Simple SSO with a token: a short script in any language, and the help center walks through it.

Agents can use single sign-on too. When you set it up, you choose who it's for, agents or customers on your portal, and the method: Simple SSO with a token, or SAML 2.0. We've tested SAML with Okta, Microsoft Entra (the new name for Azure Active Directory) and Google Workspace.

See it with your own tickets.

Every feature for 15 days. No credit card. No contract.

Setting up single sign-on

  1. Turn on the social logins you want in the portal settings. That part takes a minute.
  2. For your own app or Active Directory, get the shared secret from Cayzu and add the redirect to your login flow using the guide.
  3. Test with one user, then announce it: "log in to the help desk with your usual login."
The portal sign-in: email and password, or Google or Facebook.
The portal sign-in: email and password, or Google or Facebook. (Example workspace.)

Which plan has single sign-on, and one limit

Google and Facebook sign-in is on every plan. Single sign-on with your own app, Active Directory or SAML 2.0 is on Pro and Enterprise. See the plans.

Single sign-on has one limit: connecting your own app needs a developer, and the social logins don't.

Related: Active Directory integration, the self-service portal, and the internal help desk page.

Questions people ask

A way of logging in to one system with the account you already use for another. For the Cayzu portal, that means a customer clicks Google or Facebook, or an employee uses their company login, and they're in without a separate password.

Try it with your own tickets

Every feature for 15 days. No credit card. No contract.