× Scalekit

How Trails says yes to enterprise SSO with Scalekit.

Trails turns experts' knowledge into step-by-step guides and training videos. When enterprise customers made single sign-on a requirement, Trails added it with Scalekit instead of building it in-house. Those customers now sign in to Trails through their own identity provider.

Works with Microsoft Entra ID Okta Google Workspace + any SAML-based IdP

Record a process once. Trails turns it into a step-by-step guide and a narrated video that teams can share, embed in their LMS or knowledge base, or export.

Used by
Support, IT, HR, L&D, and enablement teams
Scalekit product
Enterprise SSO
Enterprise sign-in
Entra ID + any SAML IdP
The challenge

Enterprise customers wanted to sign in their way.

As Trails moved into larger accounts, single sign-on stopped being a nice-to-have. IT teams wanted employees signing in through the identity provider they already manage, so access to Trails is granted and removed in one place.

The decision

Build SAML support in-house, or put a proven SSO layer in front of the app. Trails chose Scalekit.

Ryo Chiba

"SSO was non-negotiable for our enterprise customers. Scalekit got us there in a fraction of the time it would have taken to build, and it's been a big part of how we close and onboard them."

Ryo ChibaCo-founder, Trails
Teams that document their work with Trails
Canary Technologies BadgePass Beacon IT Conestoga Valley School District ClassRanked DEGY Entertainment

What enterprise IT needed, and what Scalekit handles.

Enterprise SSO is more than a login button. Every customer brings its own identity provider, its own IT admin, and its own expectations about access. Scalekit takes care of that layer, so Trails integrated once.

Enterprise requirement
Handled by Scalekit
01Employees sign in with the company's identity provider
SSOSAML and OIDC connections for Entra ID, Okta, Google Workspace, and other providers.
02Each customer's setup stays separate
OrganizationsEvery customer gets its own organization and its own SSO connection.
03Customer IT can configure it themselves
Admin portalA self-serve portal where the customer's IT admin connects and tests their identity provider.
04Sign-in problems can be traced
Auth logsEvery SSO login is logged, so a failed sign-in can be traced to the right customer.

One integration. Each customer's IdP plugs in.

Trails integrated Scalekit once. Each new enterprise customer gets its own SSO connection to their identity provider, and Trails' application code stays the same.

Customer's IdP
  • Microsoft Entra ID
  • Okta
  • Google Workspace
  • + any SAML / OIDC IdP
Scalekit
Enterprise SSO
  • One connection per customer org
  • SAML and OIDC, any IdP
  • Logs every sign-in

The employee lands in their company's Trails workspace.

JM
jordan@company.comsigned in via Entra ID
Admin portal · customer IT
  1. Connect the identity provider
  2. Test the connection
  3. Enable SSO for the org
  1. 1The connection is set upThe customer's IT admin connects their identity provider in the admin portal.
  2. 2Employees sign in onceWith the Entra ID, Okta, or Google login they already use at work.
  3. 3Trails gets a verified userScalekit passes the user and their organization to Trails.
Integration
Under a week
from first line of code to SSO working, with the Scalekit team in a shared Slack channel

"We had SSO working in under a week. Any time we hit a question, the Scalekit team was right there in Slack. That's what let us say yes to enterprise customers."

Ryo Chiba
Ryo ChibaCo-founder, Trails

Enterprise SSO, in production.

Enterprise customers sign in with Entra IDTrails' enterprise customers reach the product through their own identity provider, with access managed by their IT team.
First customer live within weeksTrails' first enterprise customer was signing in through Entra ID within weeks of Trails starting with Scalekit.
No auth system to maintainSAML connections, certificates, and IdP differences sit with Scalekit. Trails' engineers stay on the product.
Each new customer is a setup stepThe next enterprise customer, on Entra ID, Okta, or any SAML provider, connects through the same integration as its own organization.
Selling to enterprise?

Add enterprise SSO once. Support every customer's IdP.

Ship SAML and OIDC sign-in for every enterprise customer, without building or maintaining it yourself.

What you get
  • SSO with any IdP+ SAML / OIDC
  • Self-serve admin portalCustomer IT connects and tests their own IdP
  • Auth logsEvery login, token, and session event
  • Free to startFirst SSO connection included