Audit panel
The Audit panel in the RebelCore™ Agent is the visible face of RebelCore™‘s governance layer. It shows the history of activity — every prompt, every applied suggestion, every dataset access — for the project you’re currently in.
It tells you who did what, and when.
Why this exists
When you put analysts to work on sensitive data via a RAG-style Agent, you need to be able to answer the regulator’s question: “Show me everyone who’s asked questions about this dataset in the last 90 days.”
The Audit panel is that answer. It’s also useful day-to-day:
- Reviewing your own activity before a hand-off.
- Investigating an unexpected result (“when did this last get touched?”).
- Confirming that someone you delegated work to actually ran the prompt.
Reasoning and User Feedback
The panel has two views:
| View | What it is for |
|---|---|
| Reasoning | Detailed workflow traces for Thinking sessions. Use this when you need the deeper step-by-step governance trail. |
| User Feedback | Short, user-friendly progress for Fast sessions. Newest activity appears at the top while the answer is being prepared. |
Neither view exposes private reasoning. They show operational steps such as checking human review, choosing a data operation, searching selected data, and preparing the final answer.
What the panel shows
For the current project, the panel typically captures:
- Sign-in events — when each user signed in.
- Agent prompts — who asked what, when, and which session it belonged to.
- Data scope changes — which datasets were active for a session.
- Curation actions — which advisor suggestions were applied in the Tree, and by whom.
- Dataset access — when a user opened a project, dataset, or spec.
Each event has a timestamp, the user who performed it, and (where relevant) the data scope it touched.
Filtering and finding
The panel typically supports filtering by:
- User — show only one person’s activity.
- Time range — last hour, last day, custom range.
- Event type — only prompts, only curation actions, etc.
- Resource — events touching a specific dataset or spec.
What the panel doesn’t show
- Other customers’ projects. Audit data is scoped to the project you’re in. To see audit across projects, you need an admin / auditor role.
- Prompt response content is shown to you only if your role allows it. In some setups, response bodies are redacted in the audit view to protect sensitive answers; the metadata (who, when, what was asked) is still recorded.
Who can see the Audit panel
Visibility is governed:
- Operators and administrators typically see the full audit trail.
- Analysts typically see only their own activity.
- Auditors are a separate role with read-only access to the audit trail across the project, without operational permissions.
See Governance & access for the full role split.