Skip to main content

Set up SSO

The context​

Laura is a systems administrator at DesignStudio, a design studio with 35 people. Her teams complain about having to log in separately to each tool: Figma, Notion, GitLab, Mattermost… Every week, she wastes time resetting forgotten passwords. She wants to implement Single Sign-On (SSO) to make everyone's life easier.

  • Each application has its own authentication system
  • Employees create weak passwords so they can remember them
  • Password resets consume IT time
  • No consistency in authentication policies between tools

Step 1 — Choose compatible applications​

Laura browses the SmartLink SSO integration catalog. She finds preconfigured connectors for Notion, GitLab, Mattermost, Nextcloud, and many more.

Step 2 — Set up SSO (15 minutes per application)​

For each application, Laura follows a step-by-step guide:

  1. She retrieves the SSO connection information in SmartLink (Entity ID, callback URL)
  2. She enters them into the admin interface of the target application
  3. She tests the connection

Step 3 — Deploy​

Once SSO is enabled, employees just have to click on the application in their SmartLink dashboard. Authentication is performed automatically via their VaultysID — a single action to access everything.

Step 4 — Remove passwords​

With SSO in place, Laura can disable password authentication on applications that allow it. The number of reset tickets drops to zero.

What changes​

Without SmartLinkWith SmartLink
One password per applicationSingle sign-on via VaultysID
Weak and reused passwordsNo more passwords to remember
Frequent reset ticketsZero password-related tickets
Complex SSO configurationStep-by-step guides for each application

Features used​