You can provide your users with more options for signing in to Zendesk Support by allowing them to use their existing social and business accounts. Social sign-ins include Facebook and Twitter, and business sign-ins include Google and Microsoft. Agents and admins can only use business single sign-on. For other types of single sign-on options, see Single sign-on (SSO) options in Zendesk.
How social and business SSO works
Social and business single sign-on allows end users to access Zendesk using their Facebook, Twitter, Google, or Microsoft accounts. When you enable the SSO methods, a sign-in button is added to your Help Center page.
Agents and admins only have access to either Google or Microsoft SSO methods. If Google or Microsoft is also enabled for end users, agents and admins can use the sign-in button on the Help Center page. If the method is not enabled for end users, agents and admins must click the Switch to agent sign-in link to use SSO.
Your users' social and business account sign-in credentials (username and password) are never shared with Zendesk. Only the primary email address contained in the social and business account is shared.
- Users select one of the social or business sign-on options on your Zendesk account sign-in page.
- Users will be redirected to their social or business sign-in page and must
enter their credentials. Note: If users are signing in with Microsoft, they can also use their Office365 credentials.
- If the credentials are valid, users will be redirected back to your Zendesk Support account.
- Zendesk will prompt the user to add an email to use as a contact.
- If the email address matches a user's email address in Zendesk, Zendesk will ask the user to enter their Zendesk password. After validated, the contact information is added to the user's profile.
- If the email address does not match a user in Zendesk, a new user will be
created, and Zendesk will send a verification email. If the user is a
duplicate of a pre-existing Zendesk user, you can merge the users (see Merging a user's duplicate
If your Zendesk account is closed or restricted, and a user tries to sign in with a business or social account email that does not exist in Zendesk, their request to authenticate will be rejected. To enable a user to sign in with a social or business account that uses a different email, you will need to add the account email as a contact in Add contact on their user profile.
For more information on modifying a user's profile, see Updating your user profile and password.
After the one-time authorization is completed, the user is seamlessly signed in to Zendesk. On subsequent visits, if the user is already signed in to the account, they will be immediately signed in to Zendesk after they click the associated social or business sign-on button. If they aren't already signed in with the social or business account, they will be prompted to.
Enabling social and business SSO
You can enable social and business SSO without any custom configuration. End users can use Twitter, Facebook, Google, and Microsoft. Agents and admins can only use Google or Microsoft.
To enable social and business SSO
- Open the password security settings for team members or end users.
- In Admin Center, click Account in the sidebar, then select Security > Team member authentication.
In Admin Center, click
Account in the sidebar, then select Security > End user
The End users command is not available until you activate the Help Center. See Getting started with Guide.
- Select each of the SSO options you want to enable.
- For team members, select Enable external authentication to display your business and SSO options.
- For end users, you have a choice of social login or SSO options.
- Click Save.
The sign-in links appear on your Help Center sign-in page.
Is there a method to restrict different brand access when using SSO, eg: Staff with an SSO login get X, Y, & Z brand access, but end-users with SSO only gain access to Brands X & Z.
As of the moment, SSO will apply to the entire account. There is no native way to restrict the implementation to different brands. However, I understand your need for this functionality and I am marking this comment as product feedback. We truly value customer feedback and your voice and votes in the community help influence future Zendesk functionality.
All the best
Looking for some direction prior to touching base with my internal IT team on how what we need to consider to move forward in our set-up with access/Help Center:
Our situation is we have end users that fall into the following segments:
1. Organization A has end users that they wish to manage via OneLogin
2. Organization B has end users that they wish to manage via Azure Active Directory
3. All other organizations have end users that will login using Zendesk authentication
...specifically so that any one of these end users can submit a ticket, track tickets and even access certain content in the HC (based on their identity/organization).
Is this "mix" possible?
And is it possible to do so in a way where the end users never see/feel a thing - their accounts in Zendesk have the accurate info and however they login, it works?
Any/all input is appreciated.
Please sign in to leave a comment.