← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesskunk-ape
Relationships
#4674 Dashboard: show the client (e.g. integration:slackwater) on activity events and run details
Opened by skunk-ape · 11/12/2026· Shipped 11/12/2026
Problem
Since serve records the client on tokens, audit events and run decisions (integrations work), a run started or approved through an integration carries client: "integration:<id>":
- audit events (
workflow.run,workflow.approve, access denials) have"client": "integration:slackwater" - the run record has top-level
client:andclient:on each approval decision next todecidedBy
The CLI shows it (swamp workflow history get <run> prints Approved by user:<id> via integration:slackwater), but the dashboard never does:
- Activity:
packages/dashboard/src/views/actor_label.tsbuilds the actor fromprincipalUsername/principalEmail/initiatedByonly, so a Slack-driven run reads exactly like one from the CLI. - Run detail: neither the initiator nor the approval decision shows the client.
So the promise that integrations keep the audit trail in swamp ("the audit trail records the person and the client") isn't visible where most people look.
Proposal
- Activity: when an event's
clientstarts withintegration:, label it<actor> via integration:<id>(or a chip). Other clients (direct:dashboard, CLI) can stay unlabelled to avoid noise. - Run detail: show the client next to who started the run, and on each approval/rejection decision (
decidedBy … via integration:<id>). - Optional: a filter on Activity by client, so an admin can see everything an integration did.
- Small related nit:
swamp workflow history getprintsApproved by user:<id>; the username would read better when known, matching the dashboard's actor label.
Notes
Found while recording the Slack integration (Slackwater) announcement demo. The data is already there; this is display only.
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse
Sign in to post a ripple.