Skip to main content

Configure SSO

The Context​

Laura is a systems administrator at DesignStudio, a 35-person design studio. 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 simplify everyone's life.

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

Step 1 — Choose compatible applications​

Laura checks SmartLink's SSO integration catalog. She finds preconfigured connectors for Notion, GitLab, Mattermost, Nextcloud, and many more.

Step 2 — Configure SSO (15 minutes per application)​

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

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

Step 3 — Deploy​

Once SSO is activated, employees just need to click on the application in their SmartLink dashboard. Authentication is done automatically via their VaultysID — one simple gesture to access everything.

Step 4 — Remove passwords​

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

What Changes​

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

Features Used​

  • 🔗 SSO Configuration — Setting up single sign-on
  • 📖 SSO Integrations — Guides for GitLab, Notion, Mattermost, Nextcloud, etc.
  • 🔐 VaultysID — Digital identity serving as a key for single authentication