Settings

The licence card, your numbers, the policy (default autonomy, quorums, drafted fixes, budgets), approval escalation, sign-in and e-mail, and the policy rules.

Settings (/settings, g s) shows the version, the install fingerprint and who is signed in, then:

PartWho changes itWhat it does
LicenceOwnersWho the licence is for, its tier and dates, the services and installs it covers and how many are used. Install or replace it, redeem a trial, Check with Warden now, and pin services that must always be covered (Licensing)
Your numbersAdminsThe figures behind the business report (Impact)
PolicyAdminsDefault autonomy for new services (shadow or off); approvers needed to raise a service (2 recommended, or 1 for single-operator installs); approvers per drafted fix (1–3, 2 recommended); the most actions per service per hour
Approval escalationAdminsThe order 3AM asks in, and after how long it moves on. It follows your connections: connecting an approval channel adds it, removing it takes it out
How people sign inAdminsIdentity provider, directory, e-mailed codes, mixed mode; group mappings; Sync now (Single sign-on)
E-mail sign-inAdminsResend or SMTP, the sender, Send me a test e-mail (Mail)
Policy rulesAdminsThe rules, first match wins, as JSON
ConnectionsA summary; managed on Connections
Policy rules
[{"match": {"action": "mysql.start"}, "deny": true, "reason": "DBA team only"},
 {"match": {"action": "restart"}, "autonomous": true},
 {"match": {"risk": "high"}, "quorum": 2, "hours": "07:00-22:00"},
 {"match": {"origin": "drafted"}, "quorum": 3}]

Lowering a quorum to 1 asks first, and says why it is only for installs one person operates.

Raising a service is refused at once, with the reason, when the escalation's channels name fewer approvers than the quorum. 3AM Doctor flags an escalation step whose channel isn't connected. A policy in /etc/3am/policy.json makes these parts read-only here. On a Keychain member, the policy may be managed from the home. Every change is in the audit log with your name.