The administrative record
The workspace keeps a record of the administrative changes made in it, readable by administrators under People → Show recent changes:
- changing someone's role, deactivating or reactivating them, and resetting their password;
- handing the workspace to a new owner;
- recovering an account with
ownbase-server recover, recorded as done by the host rather than by anyone signed in; - creating and deleting apps, replacing their bot token or signing secret, and changing where their buttons and forms go;
- adding, replacing and removing webhooks, slash commands and event subscriptions, and retrying failed deliveries;
- creating and revoking invite codes, and granting or removing a member's permission to create them;
- renaming the workspace and changing who may join it, from Workspace settings, or by the desktop app that hosts it, recorded as done by the host.
- the owner making and downloading a copy of the workspace.
- with an Enterprise license, turning single sign-on (OpenID Connect or SAML) or SCIM provisioning on or off, changing their settings, and making a new SCIM token, as well as the compliance changes.
Each entry says who made the change, to what, and when, and is written in the same transaction as the change, so neither exists without the other. A change that changes nothing — setting a role someone already has — is not recorded.
The record never holds a credential: no token, signing secret, password or invite code, and no URL given to an app, since those often carry a secret of their own. Only the host an app is called at is kept, and an invite is identified by a short fingerprint of its code. Nobody's messages are in it.
The record is kept in workspace.db, so it is in every backup, and it is not
shortened by --retention-days. Anyone who can read that file can read it, and can
change it: it is an account of what happened through the workspace, not tamper-proof
evidence against someone with access to the server itself.