Audit
Audit is the read-only record of your organization. It answers two questions: who did what, and what an agent did while it worked on a task. You can search, filter and download, but nothing you do here changes a task, a project or a setting.
It keeps two records. Activity lists every action, newest first: a person creating a task, changing a project or inviting someone, or Jaah acting on its own, shown as System. Each action records who took it, when, what it touched and how it ended. Sessions has one row per agent run on a task. A task can run more than once, after a stop, a restart or a failed attempt, and each run is its own session, naming the node it ran on, how long it took and why it ended. A run that never started a session still appears, under Attempts with no session. Efficiency totals agent time for a chosen 7, 14 or 30 days and breaks it down.
A session is Running while the agent works and Ended once it stops, or Unknown when its status was never settled; its transcript has states of its own. Treat every transcript as if it still holds credentials and customer data: only the secrets Jaah recognizes are removed.
Viewing Activity and viewing Sessions are separate permissions, and each needs your plan: Audit for Activity, Session transcripts for Sessions.
- How audit works — what Activity and Sessions record, how they relate to tasks, and the states a session and its transcript move through.
- Follow a task's sessions — every run of one task, how each ended, and the runs that never started a session.
- Find an event in the audit log — who changed what and when: search and filter Activity, then open the event.
- Compare session efficiency — where agents spend their time and money, by phase and by session.
- Find out why a session ended — narrow Sessions to the runs that ended, read the end reason and the pane log, and delete a stale row.
- See what ran on a node — narrow Sessions to one node: what it runs now and how its runs ended.
- Review what a person did — everything one person changed or opened over a period, and each sign-in's writes.
- See a record's history — everything that happened to one task, project, credential or node, by people and by Jaah.
- Review refused requests and sign-ins — requests Jaah turned away and refused sign-ins: why each was refused and where it came from.
- Check that transcripts were saved — find the runs whose transcript failed, was given up on or could not be read, and download the saved ones.
- Review a project's merge lane history — every pull request your merge lanes handled, then one project's queue, runs and history.
- Find out why the merge lane is stuck — read a project's lane state, find the run, red branch or node holding it, and get it merging again.
- Review flaky and quarantined tests — a lane's Flakes, Quarantined and Certificates tabs: which tests flaked, which no longer block a merge and until when.
- Find the session behind a branch or slot — start from a pull request's branch, a slot or a session id, and open the run's task or transcript.
- Send audit events to your SIEM — the Audit export card: a destination, its secret, a test event, pausing and removing it.
- Check whether project memory helps — compare one project's sessions with memory on and off, and see which units tasks actually read.
- Release a held memory unit — find the memory units the canon check holds back and release the ones you trust.
- See what an API key was used for — read one key's history, every call made with it and every refusal, and open a call to see where it came from.
- Choose how long your data is kept — shorten how many days Jaah keeps session transcripts, activity events and task artifacts.
Each screen and field is described in the console reference: Audit and Sessions.