Skip to content
CerberAuth CerberAuth Docs

Deletion approvals

With approvals on, no single admin can delete users: they request the deletion, and another admin approves it. It is available on the Business tier, and off until you set:

Terminal window
REQUIRE_DELETE_APPROVAL=true

How it works

Section titled “How it works”
  1. An admin who can edit users (organization admins and above) deletes one or several users. After the usual confirmation and optional reason, AUMS creates a request instead of deleting. The users stay as they are.
  2. The request appears under Approvals (also linked from Settings and from the dashboard while requests are waiting), with the users’ emails, resolved by AUMS from the provider, the reason and who asked.
  3. An admin who can delete (organization owners and instance admins) approves or rejects it, with an optional note. Approving deletes the users right away, as the approver.

The rules, enforced on the server:

  • Nobody decides on their own request, even an instance admin.
  • A request is decided once; if two admins decide at the same time, one wins.
  • A request nobody decides on within 7 days expires.

Everything is in the admin audit trail: the request, the decision, and each deletion, which names who asked. The user.delete.request, approval.approve and approval.reject events can also go to a webhook, for instance to tell your approvers in chat.