Freshdesk SSO and Security

Freshdesk SSO covers two audiences with two different sign-in problems: your agents, and your customers.

Freshdesk SSO for agents

Freshdesk supports SAML-based single sign-on with the usual identity providers, so agents sign in with the credentials they already have and access is removed centrally when someone leaves.

That last part is the real security argument. Manual offboarding is where access lingers.

Customer authentication

Separately, you can let customers sign in to your support portal with their existing account on your product, rather than creating yet another password.

This matters more than it sounds. A customer who can't log into the portal emails you instead, and if they later get in and submit a ticket as well, you have two tickets for one problem.

The settings worth auditing today

Agent roles. Who can delete, export and change automations.

Email authentication. SPF and DKIM for your support address, so replies don't land in spam.

API keys. Which agents have them, and whether integrations use a dedicated service account.

Portal access rules. Public, or restricted to registered users, and whether that choice is quietly losing you real customers.

Data export and retention, before somebody in legal asks.

FAQ

Frequently asked questions

Does Freshdesk SSO work with Azure, and what about SSL?

Yes. Freshdesk SSO Azure setups use SAML against Microsoft Entra ID, formerly Azure AD. Freshdesk custom SSL is a separate matter: it's what puts your portal on your own domain with a certificate you control.

Does Freshdesk support SAML SSO?

Yes, with the common identity providers, on the plans that include it.

Should the customer portal require login?

It depends on your product. Requiring registration cuts spam and loses some genuine contacts, who then email you instead.