Activity Feed in the Admin PortalCopy Anchor Link

The Activity screen is one feed for everything that happened across your cases and your team: part ledger, part monitor. Nothing ages out: the record goes back to your first activation.

It opens on Key activity, so the first thing you see is the work your team finished rather than every keystroke behind it. Everything else is still recorded, one click away.

Key activity, or everythingCopy Anchor Link

Above the type chips there is a switch with two settings.

• Key activity (where the screen opens) is the work worth a look: a bulk task that finished, an Insight generated, a case assessment run, a report downloaded, a case activated or deactivated, a Case Context created or approved, an overage incurred, tokens bought, a plan changed, an invoice issued, a decision taken in the portal, a role assigned, an email that failed, and a moment when no AI model was available.
• Everything adds the register underneath: every document scanned, every prompt saved and pinned, every comment deleted, every field connected, every chat started, every autosave of a Case Context, every routine email, and each monthly token grant and free daily claim.

Nothing is ever dropped. When the quieter view is holding events back it says so under the chips, with Show everything beside the count. Your choice sticks in your browser until you change it, and the download always saves exactly what you are looking at.

What is in the feedCopy Anchor Link

Each row shows the time, what happened, the case, who did it, the tokens moved and, when money moved, the amount in your region's currency.

Case actions taken in the portalCopy Anchor Link

When an organization admin changes a case's plan, cancels a scheduled change, books or cancels a deactivation, or schedules or cancels a data deletion from the case page, the feed shows it in two places:

• Under Roles and access, the request, then its outcome: done from the portal, failed, refused (for example, the case was not in a state that allowed it, or the typed case name did not match), or not permitted for the admin's role. A request is always recorded before anything changes.
• Under Case lifecycle, the change itself, as the case's own record shows it.

Opening a case's billing reports appears under Roles and access as Billing report downloaded. Marking a case as a demo or test case, or putting it back on the invoice, appears there too. So does every change to your organization's prompt templates, named by the template's title.

Reports that left a caseCopy Anchor Link

Every Insight, Case Context, Bulk Task History report and prompt history that someone downloads is recorded under Report downloads: who, which case, which report, which format and when. It answers "what left this case, and when?" without keeping a second copy of anything: the row holds the reference (for example IN014), the format and a few counts, never the text of the report.

Automatic model routingCopy Anchor Link

When someone has automatic model routing on and the AI model they are using is busy, Claira answers with another approved model in your country. Each time that happens, the feed shows a Model switched row under Model routing: the person whose request it was, the feature (a scan, Agent Mode, an Insight, Case Context and so on), the model that was busy or not responding, and the model that answered. A bulk task run in the browser gets one row for each pair of models, with the number of documents that moved. If every model was busy, the row reads No model available, and that person saw the usual busy error.

These rows record which models were involved, never the document or the answer.

Deleted commentsCopy Anchor Link

When someone deletes a comment on a prompt or on a bulk task, the feed shows Prompt comment deleted or Bulk task comment deleted: who deleted it, which case, whose comment it was (only its author can delete one), the task number for a task comment, and Added by the Agent when Agent Mode had written it. The comment's text is gone: the record never keeps it. These rows are part of Everything, not Key activity.

FilteringCopy Anchor Link

• Key activity / Everything decides how much of the record you see. See Key activity, or everything above.
• Type chips switch a type off to hide it from the feed and from the counts. Every type starts on. The choice sticks in your browser until you change it.
• Search matches names, references (SC118, IN014, MG008), labels and users.
• Filters narrows the feed by date (any time, or the last 7, 30, 90 or 365 days), by user and by case. The button shows how many filters are on, and Clear filters removes them.
• The download button saves the feed as filtered, as a CSV file.

Who did itCopy Anchor Link

Not every event records a user. The monthly token grant, background scan phase changes and clean-ups are system events with no actor, and a few events only get a name from the thread or Insight they belong to. The feed shows System rather than inventing a name, and a name is a strong hint rather than an audit-grade attribution.

---

Need help? Contact us at support@claira.to.