Settings

The Settings page controls global gateway behavior. It’s in the sidebar for admins, and only admins can change it. Saving most groups needs MFA on the request (session timeout and VCS/CI defaults need a step-up).

Session Timeout

Configure the sliding inactivity timeout for browser sessions (default 5 minutes). It applies to sessions created after the change. CLI sessions always last 90 days from their last use.

Enter the timeout in minutes
Click Save
(Optional) Click Clear to revert to the default

MFA Requirements

Global MFA policy for all users:

Require MFA for all users (default on). Off, MFA applies only to users who have enrolled a method
Trusted Device TTL (days) (default 30)
Step-Up Window (minutes) (default 10)

Changes apply at once, on every gateway instance.

Destructive Actions

Allow destructive actions (off by default) controls whether destructive rack operations are allowed at all: while it’s off, the gateway refuses deleting an app (“Destructive rack actions are disabled by policy”), whatever the caller’s role. Stopping a process isn’t affected. This is a global safety switch.

Deploy Approvals

Enable deploy approvals turns the deploy approval workflow on or off, and Approval Window (minutes) (default 15) sets how long an approved request can be used to deploy.

Default VCS & CI Providers

Set the defaults for app-level deploy approvals:

VCS provider (currently GitHub)
CI provider (currently CircleCI)

These defaults are used when an app does not specify its own provider settings.

App Settings (Per-App)

App-specific settings are not on this page. Go to Apps → {app} → Settings to configure:

VCS/CI deploy settings (repo, branch, approval job name)
Protected and secret environment variables
Environment variables shown in audit logs: every other env value is [REDACTED] in the audit log and Slack (see Secret Redaction)
Approved deploy commands
Service image patterns

Deploy Approvals - CI/CD approval workflow
Account Security - MFA setup and trusted devices