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 spends time resetting forgotten passwords. She wants to implement Single Sign-On (SSO) to simplify everyone's life.

The problem without VaultysHub​

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

With VaultysHub​

Step 1 — Choose compatible applications​

Laura consults the SSO integration catalog of VaultysHub. She finds pre-configured connectors for Notion, GitLab, Mattermost, Nextcloud, and many others.

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 VaultysHub (Entity ID, callback URL)
  2. She enters them into the administration interface of the target application
  3. She tests the connection

Step 3 — Deploy​

Once SSO is activated, employees just need to click on the application in their VaultysHub dashboard. Authentication is done 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 it changes​

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

Features used​