All Documentation

Documentation Everywhere else

Audit events: channels and the warden

The audit catalogue's channel events — a discussion becoming a channel, who answered a post, work started from a thread — and the warden's stops and Allow Once.

What happened in a channel on the Mac: a discussion becoming one, who was chosen to answer a post, and work started from a thread. The web's channels are recorded with the runs they start. Then the warden: an action it stopped, and one the person let run once anyway (Allow Once, or running again with it allowed), with who did.

Channels and the warden

TypeReported byWhenDetail carries
session.channelMacAn In-turns discussion became a channel; what was said stays above the feed, read only (lib/channel.js).history
channel.routedMacA channel post was routed: which AI answers, why, and where the answer goes — or nobody (lib/channel.js).targets, why, routed, place
channel.buildMacA build session was started from a channel thread.thread, build, on
channel.ticketMacA ticket was created from a channel thread or message, with no run.thread, ticket
channel.thread_ticketsMacEvery New Thread Is a Ticket was turned on or off for a channel.on
channel.scopeMacA channel was moved to Organization Channels, or out of them to stand in no project.scope
warden.stoppedMac and serverThe warden stopped an action: off the job, or an injected instruction.tool, why
warden.allowed_onceMac and serverThe person let one stopped action run once.tool, why, key, by, from

What these do not carry

Never a post's words: a thread by its id, an AI by its seat, a ticket by its discussion.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.