Getting started with Zendesk Suite - Part 4: Managing user access, security, and authentication

What's my plan?

Suite

Team, Growth, Professional, Enterprise, or Enterprise Plus

Articles in the series

• Introduction: Getting started with Zendesk Suite
• Part 1: Accessing Zendesk Suite admin settings
• Part 2: Adding team members
• Part 3: Understanding how end user accounts are handled
• Part 4: Managing user access, security, and authentication
• Part 5: Adding support channels
• Part 6: Routing incoming support requests
• Part 7: Managing support requests during non-business hours
• Part 8: Guaranteeing customer support expectations with service level agreements
• Part 9: Reporting on support activity
• Part 10: Enabling customer satisfaction ratings
• Part 11: Leveraging AI features with Zendesk
• Part 12: Using the Zendesk developer platform to extend your support solution
• Part 13: Rolling out your Zendesk Suite support solution
• Part 14: Additional features

Zendesk offers several ways to authenticate team members and end users, including standard Zendesk sign-in using email and password, third-party authentication through services such as Google and Microsoft, and single sign-on with identity provider services such as OneLogin and Okta.

Because users may have different security requirements, Zendesk gives you the flexibility to allow multiple authentication methods for each type of user and let users choose how to sign in.

To maintain security, your team members must be signed in and authenticated to access any part of the Zendesk Suite. Team members sign in once per session and then access the products they have access to via the product tray.

Your customers may not have to sign in, depending on how you set up end user access to Zendesk Support. You can require end users to sign in and be authenticated to use your help center and submit support requests via the support request form.

In addition to the support request form in your help center, you can embed Zendesk Support into your websites and mobile apps. You have the option of requiring end users to sign in for messaging on your website so that you can authenticate who they are.

See Global security and sign-in resources for more information about configuring other security settings, such as the password security level, two-factor authentication, and IP restrictions.

Continue to Part 5: Adding support channels.