Skip to content

Settings & Profile

The org-level mail server and authentication posture, and your personal preferences.

Settings

Where: Settings · Who: MANAGE_GATEWAY to edit the mail server; platform admins read the auth posture · Editions: all

Settings Mail server (SMTP) HOSTsmtp.example.com PORT587 USERNAMEmailer@example.com PASSWORD•••••• (write-only) Send test Save STARTTLS Authentication SSO (OIDC)on Form loginoff Break-glass Basicon Read-only. Set at deploy time, never from the dashboard.
Settings. The org's SMTP form (with a write-only password and a send-test) beside the read-only authentication posture card.

Settings holds the small set of things configured from the dashboard (as opposed to at deploy time).

Mail server

The org's SMTP server, used to send notification emails and emailed reports:

  • Host, port, username, and a write-only password (it is never read back), the from address, and a STARTTLS toggle.
  • A send-test button to confirm it works before you rely on it, and a clear action to remove it.
  • The platform admin picks which org to configure; a member is locked to their own.

Authentication

A read-only posture card (platform admins) reporting what sign-in methods are live: SSO (OIDC), the local form login, and the break-glass Basic admin, read from /admin/auth/methods.

Auth is configured at deploy time, on purpose

There are deliberately no write controls for authentication here. SSO issuer, audiences, and whether form login is enabled are set in the deployment configuration (and at your IdP), never from the dashboard, so a compromised dashboard session cannot weaken sign-in. See authentication and How it is deployed ▸ SSO.

Profile

Where: Profile (top-right avatar) · Who: everyone (it is your own account) · Editions: all

Your personal page:

  • Identity (name, email). When SSO is configured this is managed at your IdP (Keycloak), so it is shown read-only here; you change it there.
  • Preferences stored locally in your browser: theme (light/dark, follows OS by default), timezone, and density.
  • Security: your MFA and break-glass posture (MFA is an IdP realm policy, not gateway config).
  • Recent activity and active sessions.
  • Sign out, which returns you to the login screen (and, under SSO, ends the session chain).

Back to the section map, or read How it is deployed →.