Omniscio

Team Chat — an admin removing someone else's message

A company owner or admin, and the manager of a channel, can delete anyone's message in that channel. The message is not just gone: a small grey line stays where it was saying it was removed by an admin, and one audit entry records who removed it, whose message it was, and when — never what it said. Direct messages stay author-only.

On this page

Who can do it

  • A company (organisation) owner or admin, anywhere in that company.
  • A chat-workspace owner or admin, anywhere in that workspace.
  • The manager of that channel, in that channel only.

They see Delete on someone else's message from the ⋯ menu and from right-click, in a channel and in a thread. Everybody else sees no such action — a plain member keeps only their own delete.

Direct messages stay author-only. There is no moderation inside a DM, whoever you are.

What the person who removed it sees

The message is replaced in place by a small grey line:

This message was removed by an admin

The row keeps the author's name and avatar, so it is still obvious whose message was removed, and it carries none of the original content: no text, no attachments, no link previews, no reactions, no edit or delete controls.

There is deliberately no "Re-send" offer on this path. The author's own delete offers it because re-posting your own text is a sensible reversal; re-posting someone else's removed text under a moderator's name is not.

What is recorded

Every removal writes one audit entry, and the server writes it — a client can never write its own audit row, and the removal cannot happen without the entry being attempted:

Field What it holds
who the moderator's user id
whose the message author's user id
where the workspace (company or chat workspace) and the channel
when the time of the removal
how big the removed message's length in characters

The message's text is never recorded. It is already gone from the message by the time the entry is written, and copying it into an audit trail would defeat the removal.

Only owners and admins can read the trail. A channel manager may remove a message but cannot read the audit entries.

How it works

The removal is a rewrite in place, not a document delete: the message keeps its place in the conversation so the grey line can be drawn there. The rewrite blanks the text, mentions and attachments and stamps removedByAdmin / removedByUid / removedAt. A Cloud Function sees that rewrite and does the rest — reconciles the channel's last-message preview, queues the orphaned attachment files for deletion, and writes the audit entry.

The ordering matters and is enforced: the Firestore rules allow the rewrite only in exactly that shape, only for the roles above, only in a non-DM channel, only for a message the caller did not write, and only once. Everything else is refused by the server, whatever the app shows.

What else goes with it

The removal is not just the text. The message loses its link previews, its emoji snapshot, its forwarding note and its channel references outright, its attachment files are deleted from storage, its earlier edited versions are purged, and the channel and thread previews switch to the same wording. Nothing of the message is left anywhere a reader could reach.

  • Team Chat — the feature this belongs to
  • Every removal is reversible in the ordinary sense: the author can post again, and the moderator can never un-remove someone else's message.

Last verified 2026-11-20