Skip to main content

Sign-in & identity

People sign in once at the vastframe Edge, at auth.<your-domain>, and the session covers the console and every app in the organization. Apps never see passwords. This section explains the sign-in methods and how to set each one up.

Choose a method​

MethodBest forWhere it's configuredCost
Microsoft Entra ID, self-hostedInstallations in your own AzureInstallation settings, at install timeIncluded
Email linksTrials and small teams without an identity providerAdmin › Sign-inIncluded
Microsoft Entra IDvastframe cloud organizations on Microsoft 365Admin › Sign-inIncluded
Other OpenID ConnectGoogle Workspace, Okta, Auth0, KeycloakAdmin › Sign-inIncluded
Enterprise SSOSAML identity providers (Okta, Ping, ADFS…) and SCIM directory syncAdmin › Sign-inNeeds WorkOS enabled on the installation and, on a licensed organization, a plan that includes SSO

Self-hosted vs vastframe cloud​

  • Self-hosted installations sign in with the Microsoft Entra ID tenant the installation was set up with. Admin › Sign-in shows this read-only: "This organization signs in with the Entra ID the installation was set up with. It is changed at install time, not here."
  • vastframe cloud organizations start with email links. An Org Admin can switch to Entra ID, another OpenID Connect provider or enterprise SSO at any time.

Changes apply to new sign-ins within a few seconds. People already signed in stay signed in.

Membership​

On a vastframe cloud organization whose people are managed in vastframe, only its members get in. Members are the people in Admin › People, added one by one, by CSV import, by directory sync, or automatically when you verify an email domain and allow anyone on it to join.

Someone who signs in successfully at your identity provider but isn't a member sees "Not a member yet" and is asked to contact IT.

Sessions​

  • One session covers the console and every app on the organization's domain.
  • Sessions last 8 hours by default. A session isn't revoked server-side, but every request still passes the access check, so a person who is turned off loses access within seconds.
  • /_tc/auth/logout on any app signs out of every app, and of the identity provider when it supports sign-out.
  • A session made in one organization is ignored on another organization's domain.

Keep a way in​

Emergency access lets Org Admins sign in with an email link if your identity provider breaks. Note the link before you switch methods.

Was this page helpful?