Identity
Federate sign-in with your identity provider, then let it manage Cephable membership automatically.
Two pieces, in this order.
Single sign-on federates authentication: your users sign in with your identity provider instead of a Cephable password, on every client. SCIM then lets that same provider manage who is a member, so a leaver's seat is freed as part of offboarding rather than as a task somebody has to remember.
SSO comes first — SCIM assumes federated identity.
Neither of these is a self-serve page of fields. Cephable configures them for your organization in partnership with your IT team, through a short exchange of identity-provider details. The pages below document how each works and exactly what you will be asked for, so you can have it ready.
Start either one — or request a change to an existing configuration — by emailing support@cephable.com.
Domain verification is what routes work email addresses to your identity provider, and it is part of the SSO setup rather than something you do separately. Doing it after people have created personal Cephable accounts means merging accounts later — so open the thread with support early enough that the exchange finishes before your pilot starts.
In this section
Related
SCIM provisioning
Let your identity provider create and remove Cephable seats automatically. Enabled by Cephable together with your IT team.
Single sign-on
Route your users to your own identity provider when they sign in to Cephable, on every client. Configured by Cephable together with your IT team.
Deploying at scale
What a Cephable rollout involves — getting the app onto devices, getting people into your organization, and the device policy to check first.