Admin actions on your account
The dashboard surfaces a small number of admin-level actions that affect your account’s billing state. This page is the operator-readable view of what happens behind the scenes when an admin uses one of those actions: every administrative change is recorded, with a required note explaining why.
Audit
Every admin grant of subscription time is audit-logged with a required notes field, captured at the moment the admin clicks Confirm in the grant dialog. The dialog labels the field as “Notes (required, internal)” and warns: “Every admin grant is audit-logged with this note so the reason for the grant is permanently traceable.”
Two specific admin actions write to the audit log today:
- Subscription grant — an admin extends your account’s
expires_atby a chosen number of days or months. The audit row records the admin user, the extension amount, the resulting new expiry, and the operator-supplied note. The dashboard surfaces the explicit reminder on the dialog: “No payment will be recorded. This action is logged in the audit trail.” - Grandfathering — a one-shot operation that grants a fixed extension to a cohort of historical accounts. The audit row records the cohort definition, the extension amount, and the operator-supplied note.
The audit log is append-only and immutable. If you ever need to know “who extended my subscription, when, and why?”, the answer is in the audit trail; ask the on-call admin to surface the relevant rows for your account.
This page is the user-facing view of the same audit semantics surfaced internally: what gets recorded, what fields are required, and what guarantee the audit trail provides.