Skip to main content

Auth overview

Auth controls how end users enter and access your app. It is app-scoped, so each app can have its own sign-in methods, policies, branding, SSO, MFA, organization access behavior, legal consent, hooks, and directory sync.

Switera Auth overview with setup state and Auth tabs
The Auth overview shows the current Auth state and links to the specific tab that needs setup.

Auth sections​

The overview shows Configured when at least one sign-in method is enabled. This includes social-only apps; it does not require an organization. Test the configured method in your app before treating sign-in as working. The end-user count includes individual accounts outside organizations.

Common sections are visible in the Auth navigation. More settings contains Branding, Organization Access, Enterprise SSO, Auth Hooks, Directory Sync, and Compliance. On mobile, use the Auth section selector.

TabUse it for
OverviewCurrent Auth state, recommended next action, and core areas.
End UsersPeople who can sign in to the app.
Sign-in MethodsPassword, email sign-in, magic links, passkeys, username, phone, and password policy.
Social ProvidersGoogle, GitHub, Microsoft, Apple, and other provider-based login.
Enterprise SSOSAML, OIDC, LDAP, and enterprise identity provider connections.
SecurityMFA, session behavior, CAPTCHA, step-up authentication, and privileged sessions.
BrandingHosted Auth appearance, logo, colors, message, and page copy.
Organization AccessOrganization membership behavior, signup rules, and role model.
Auth HooksSynchronous hooks that inspect, block, or modify sensitive Auth flows.
Directory SyncPeople, groups, and membership sync from enterprise directories.
ComplianceTerms, privacy policy, and consent requirements.
  1. Open Sign-in Methods.
  2. Enable one primary sign-in method.
  3. Keep email verification enabled for real users.
  4. Open Branding and add enough product identity for end users to trust the page.
  5. Open Compliance if sign-up requires terms or privacy consent.
  6. Sign in through your app with a test end-user account. Test an organization invitation too if the product uses teams.
  7. Check the resulting end-user account and session. Configuration alone does not prove the flow succeeded.

Generate integration recipes​

Expand SDK integration on the Auth overview to find Integration recipes. Use it after the OAuth client exists and before wiring your app manually.

The panel generates:

  • .env.example entries for your selected stack
  • an app provider or token-introspection middleware snippet
  • a protected page or API route snippet

Supported launch stacks are SvelteKit, Next.js, React, Vue, and Express API. The browser/framework snippets use public Auth settings only: Switera base URL, Connect client ID, app slug, and redirect URI. Secret app credentials stay on your backend and are not needed for hosted end-user login.

For Express API services, the generated snippet validates bearer tokens against Switera and protects a selected route. Pair that backend route with one of the browser/framework Auth SDKs in your frontend.

Auth is app-scoped​

Changing Auth settings in one app does not configure another app. Always confirm the app name in the sidebar before changing sign-in methods, provider credentials, SSO, or security policy.

What to configure first​

Use this order for most apps:

  1. Sign-in Methods so users can enter the app.
  2. Email so verification and recovery messages can be delivered.
  3. Branding so hosted Auth feels trustworthy.
  4. Organizations only when your product uses shared customer accounts or tenant-scoped services.
  5. Security so MFA and sessions match the risk level.
  6. Social Providers or Enterprise SSO when provider credentials are ready.
  7. Hooks or Directory Sync when backend or enterprise lifecycle automation is required.
Switera organization access settings for Auth
Organization Access is where Auth behavior meets customer account membership, signup rules, and the role model.

When to add advanced controls​

Add advanced controls when the app needs them:

  • social login after provider credentials are ready
  • SSO when selling to organizations that require identity provider login
  • MFA when the app handles sensitive accounts or admin actions
  • Auth Hooks when your backend must participate in login decisions
  • directory sync when enterprise organizations expect automated user lifecycle management

Related pages: