Skip to main content
Start Free Trial

Configuration

Use the Guardhouse dashboard to configure one tenant. Application developers then copy the resulting issuer, client, resource, and scope values into their own applications.

Availability

The controls you see depend on your role, Guardhouse plan, and deployment type. Managed defaults and custom domains apply to Guardhouse Cloud; infrastructure settings for a self-hosted deployment are owned by its operator.

Choose a task​

  • Applications and API resources — register browser, native, and service clients; define audiences and scopes; and choose token validation.
  • Authentication — configure login methods, signup, MFA, passkeys, passwordless login, and social providers.
  • Users, roles, and permissions — manage user access and keep dashboard administration separate from application authorization.
  • Branding and domains — customize hosted pages, organization details, profile options, and the public tenant domain.
  • Providers and webhooks — connect email and object storage, customize email templates, and deliver signed events.
  1. Choose managed or custom email and storage providers.
  2. Confirm the organization name, legal links, and public domain.
  3. Configure at least one login method and decide whether signup is open or invite-only.
  4. Create API resources and scopes before assigning them to clients.
  5. Create clients and copy their configuration into each application.
  6. Define permissions and roles, then invite a small set of test users.
  7. Test login, logout, token validation, email delivery, and webhook delivery before production rollout.

Dashboard settings versus application settings​

The dashboard is the source of truth for registered redirect URIs, origins, token lifetimes, scopes, authentication policies, and provider credentials. Your application remains responsible for initiating the correct OAuth/OIDC flow, validating tokens, enforcing authorization, and protecting its own secrets.

For production hardening and deployment ownership, continue with Security and Guardhouse Cloud and self-hosted deployments.