Across every product · One Login

One login.
Every product, hub, and region.

Sign in once. Your session resolves to the right scope automatically — whether you're switching between products, jumping into a client's workspace, or accessing a hub hosted in a different region. No re-authentication. No separate credential sets.

See a walkthrough

What it covers

One session handles every context switch.

The session model is scoped per hub — but switching context doesn't mean starting over.

App switching

One session covers every Sympl product — Sympl · CMMS, Sympl · Signal, Sympl · Project. Navigate between apps without a separate login per product.

Hub & instance switching

If you manage multiple hubs — an MSP with client workspaces, a corporate account with plant-level hubs, or a franchisor with franchisees — switch context from the avatar menu. No re-authentication.

Cross-region access

International hubs are hosted in their own zone for data residency compliance. Your session still resolves to the right regional instance automatically — you see the right data, in the right zone, from one login.

SSO / identity provider

Connect your organization's identity provider — Microsoft Entra, Okta, Google Workspace, or any SAML 2.0 / OIDC provider. Provision and deprovision users from your existing directory.

How it works

Identity decoupled from any specific product or region.

01

One stable identity

Your user identity is global — it survives provider migrations, product additions, and hub changes. One row, one ID, forever.

02

Memberships per hub

You hold a membership in each hub you can access — with its own role and scope. Switching hubs resolves the right session without a new login.

03

Sessions are hub-scoped

Each active session is bound to one hub. Switching opens a new scoped session for the target — your existing sessions remain active.

04

Regional instances, unified auth

The auth layer is global. A hub hosted in EU-West still authenticates through the same login flow — your session is then handed off to the right regional instance, keeping data in-zone.

One login across everything you manage.

Whether you're running one site or a portfolio of hubs across multiple regions — it's one set of credentials, one session, one place to switch context.

See a walkthrough