Skip to content

Audit log

The Audit log tab is a record of the management actions taken in your workspace, newest first. It answers who did what, to what, and when. Nobody can edit or delete entries from Chat Administration.

Chat permission: administration.read

Administration, then Audit log. The table has four columns.

Column What it shows
When The time of the action
Action The action name, from the list below
Actor Who did it: a person (their user id), a backend client (its client id), or SYSTEM for Chat itself
Target What was acted on: a type such as CONVERSATION, MEMBER, MESSAGE, ROLE, SETTINGS or TENANT, and its id

Select Load more to read older entries. The API returns 50 items per page by default and at most 100 items.

Action What it means
CONVERSATION_CREATED A direct conversation or a channel was created
GROUP_CREATED A group was created
CONVERSATION_UPDATED A conversation or channel was renamed, changed, archived or reactivated
GROUP_UPDATED The same, for a group
CONVERSATION_DELETED A conversation was deleted
MEMBER_ADDED Someone was added to a conversation, or joined a public channel
MEMBER_REMOVED Someone was removed from a conversation, or left it. The reason says which.
MESSAGE_DELETED_BY_MODERATOR Someone with messages.delete deleted another person’s message
ROLE_PERMISSIONS_UPDATED A role’s Chat permissions were saved, with the permissions before and after
SETTINGS_UPDATED A setting such as message retention was changed
IDENTITY_REFRESH_REQUESTED Someone selected Refresh from Identity Server
ADMIN_LOGIN A person opened Chat Administration for the first time in a sign-in session

Older workspaces may also show ROLE_PERMISSIONS_RESET, from an earlier way of managing roles. APPLICATION_CHAT_ENABLED, APPLICATION_CHAT_DISABLED and ADMIN_ACTION exist as action names but this version does not record them. Switching Chat on or off is recorded by the Identity Server.

Sending, editing and reacting to ordinary messages are not recorded. Who holds which role is recorded by the Identity Server.

  • A person acting in the Chat app, or through the API with their own token.
  • A backend client. Everything your backend does through the Chat API, such as creating conversations or adding members, is recorded with the client as the actor.
  • SYSTEM, for actions Chat takes by itself, for example removing a person from conversations after they left the workspace.

Management actions made by your backend client are recorded in the same way as the ones you make in the UI.

The tab itself has no filter boxes. The Chat API can filter by action and by the user who acted, and pages with a cursor. Each entry also carries the application, the before and after values of a change, and request details. See read the audit log.

Role assignments and sign-ins are audited by the Identity Server: see the Identity Server documentation.