System configuration
Beyond the deploy-time environment configuration, Ticketra exposes runtime settings that admins manage from the UI, stored per tenant in the system config store.
What you can configure
| Area | Examples |
|---|---|
| Session policy | Session TTL (hours) for the tenant. |
| Account lockout | Lockout thresholds / tiers for failed logins. |
| CTI cache retention | How long threat-intel verdicts are cached. |
| Audit retention | How long audit events are kept. |
| Branding | Report logo. |
| SMTP & notifications | See notifications. |
| LDAP | See LDAP / AD auth. |
How to change settings
- Sign in as an
ADMINorSUPER_ADMIN. - Go to Admin → Configuration.
- Adjust the relevant setting and save.
Changes are scoped to the current tenant (system users operate within the tenant they've selected).
Permissions
| Action | Permission |
|---|---|
| View configuration | config:read |
| Modify configuration | config:modify |
Deploy-time vs runtime
Secrets and connection settings (database, JWT secret, allowed origins) are set at deploy time via environment/secrets — see the Configuration reference. The UI settings here are operational policy that can change without redeploying.
Related
Was this page helpful?