Security and access
Sign-in, single sign-on, roles and permissions, audit, TLS, and running behind a reverse proxy.
Sign-in options
| Option | Where | Notes |
|---|---|---|
| Local accounts | Settings → Users | Email and password, with two-step verification (TOTP) |
| Single sign-on | Settings → SSO/LDAP | Microsoft Entra ID, Google Workspace, Authentik, Keycloak, Okta, any OpenID Connect provider, SAML 2.0 |
| Active Directory / LDAP | Settings → SSO/LDAP | Directory username and password over LDAPS or StartTLS; groups (nested ones too) map to roles |
| SSO only | Settings → General → Local sign-in | Turn off passwords; keep up to 10 break-glass accounts for when the identity provider is down |
Built-in roles
| Permission | admin | operator | viewer |
|---|---|---|---|
| View the dashboard and monitoring | ✓ | ✓ | ✓ |
| Use the assistant | ✓ | ✓ | — |
| Approve changes | ✓ | ✓ | — |
| Approve dangerous actions | ✓ | ✓ | — |
| SSH and RDP sessions | ✓ | ✓ | — |
| Scheduled jobs | ✓ | ✓ | — |
| Connectors, AI providers, users, settings | ✓ | — | — |
| Audit log, backups | ✓ | — | — |
Create custom roles in Settings → Roles from about 20 permissions, optionally limited to certain connectors or tags. SSO groups can map to roles.
Ready-made roles and access rules
Start a new role from Certificate admin, Security admin, Change approver, Patch operator, Help desk or Auditor, then change anything. Access rules tailor what the assistant may do for a role:
| Rule | Example |
|---|---|
| Deny | Nothing dangerous (deletes, wipes, resets) |
| Allow only | Only checking for and installing updates, and reboots |
| Time window | Changes only Monday to Friday, 20:00–23:00 |
| Needs a second approver | Anything on servers tagged production: the requester can’t approve their own |
| Single sign-on only | Changes only for people who sign in with SSO |
Settings → Roles & permissions → Who can do what shows, for a person, a tool, a connector or a permission, which roles allow it and who has them.
A viewer can’t use the assistant by default. Add Use the assistant to a role to let people ask questions without being able to approve changes.
Audit
Every action, approval, remote session and setting change is in the audit log, with who did it and from where: web, Telegram, voice, API or a scheduled job.
TLS
TLS_MODE | Port 80 | Port 443 | Use when |
|---|---|---|---|
self-signed (default) | Redirects to HTTPS | Certificate made on first start | Trying it out, internal use |
custom | Redirects to HTTPS | Your certs/tls.crt and certs/tls.key | You have a certificate from your own or a public CA |
off | Plain HTTP | — | Behind Traefik, nginx or Caddy |
Behind a reverse proxy
TLS_MODE=off
PUBLIC_URL=https://ops.example.com
TRUSTED_PROXIES=172.18.0.0/16
| The proxy must | Why |
|---|---|
Forward X-Forwarded-For and X-Forwarded-Proto | Correct addresses in the audit log and sign-in limits |
| Support WebSockets | Remote SSH and RDP sessions |
Not buffer text/event-stream | Chat answers stream as they’re written |
Never set
TRUSTED_PROXIESto*. Anyone could then fake their address and get around sign-in limits.