Skip to content
Ronja Docs

Activity log

The Activity Overview answers “what is my team actually doing in Ronja?” — in counts, never credits. Open it from the admin sidebar under Usage & Control. Credit figures live on the separate Usage page; this page never shows them. That split is deliberate: counts cross to admins here, spend stays on the billing surfaces.

Two controls sit at the top of every tab:

  • A time window pill — 24h · 7d · 30d · All — that scopes most numbers.
  • A scope pill — Tenant (your whole organization) or a single Workspace, with “← Back to tenant view” to return.

The page has six tabs.

Overview

Section titled “Overview”

The starting view: your team’s health and headline counts.

  • An automation health strip — “All clear. No automations with issues in this window.” or “Needs attention — N automations with issues” with a “View automations →” link.
  • Hero cards: Automations, Total activity, and Active users (out of total seats).
  • Support cards: Workspaces, Total features, Total rows, Total processing, and P95 duration.
  • Feature composition (the private / workspace / organization split) and Storage.
  • A Themes band (sentiment bar, prompts, sessions, completion) with “See themes →”.
  • An Activity by kind stacked-area chart.

Usage

Section titled “Usage”

Counts only — no credit figures anywhere. This is the tab for board-slide numbers.

  • Value delivered — “The numbers for a board slide”: total activity, rows processed, active workspaces.
  • Activity by kind and a Rows processed spark chart.
  • Processing operations — “What Ronja did the work for”: Queries (interactive data queries), Workflow runs, Table builds, and Chart renders.
  • Most popular tables — the tables read most often, with “last read date”.
  • Data app usage — a table of App · Opens · Viewers · Last opened · Queries. Opens count live serves only; author draft previews are excluded.

Themes

Section titled “Themes”

An AI-inferred read of what people ask Ronja (tenant scope only).

  • Hero counts: Prompts, Sessions (with completion %), Re-engagements, and a Sentiment mix (an “AI-inferred” pill splitting Satisfied / Neutral / Frustrated / Unclear).
  • Top themes — a rolling ~14-day AI snapshot that refreshes on its own roughly every four hours. It ignores the time-window pill by design.
  • A Sessions table — Theme · Sentiment · Depth · Privacy (Shared / Private) · User · Started — with expandable rows showing the summary, sources, tools, and notes used.

Users & workspaces

Section titled “Users & workspaces”

Adoption and engagement.

  • Engagement heroes: Active in window (N of total, % of seats), Pending invites (“Invited · never logged in”), and Dormant users (“Logged in once · idle > 30d”).
  • An Active users over time chart (Admins / Non-admins / Other).
  • An Adoption band (the Active / Dormant / Invited share).
  • An All users table — search by name or email, filter by status (All / active / invited / dormant), and sort by Last seen or Name. Columns include Last seen (“Not yet” for people who’ve never logged in) and the count columns Queries · Runs · Active days.

Log

Section titled “Log”

The raw, date-grouped feed of everything that happened.

The Log tab: a date-grouped operations feed with type, status, and user filters The Log tab — every logged operation, filterable by type, status, and user.

  • Search the feed with the Search the log box.
  • Type chips filter by operation: All · Table Build · Analysis · Query · Sync · Workflow · Automation · Scheduled · Exploration · Feature · Connection · Memo · File · Data app · Admin.
  • Status chips: All · running · completed · failed.
  • A user filter menu narrows to one person.
  • Each row shows a status dot, the operation kind, its title, the user, the time, and the duration, and expands for detail. Load more pages through older activity.

When nothing matches, you’ll see “No activity matches the current filters.” — clear a filter or Load more to keep searching.

Traces

Section titled “Traces”

The list of cross-primitive execution traces — the run-level counterpart to the Log.

  • This tab is always tenant-wide (“Showing N · tenant-wide”) and ignores the workspace scope.
  • Filter the list with the Search traces… box, the Kind chips (All kinds / Automation / Manual run / Workflow / Agent / Alert), and the Health chips (Any health / Done / Degraded / Failed).
  • One row per trace: its kind, name, status badge, an “N issues” count, and a timestamp.
  • Click a row to open its full timeline at its own trace page. Load more pages through older traces.

The Traces tab with a search box and Kind and Health filter chips above the execution-trace list The Traces tab — search and filter every run across the organization by kind and health.

Traces carry counts only — no cost or credits. For reading a single run end-to-end, see Monitor runs and traces.

See also

Section titled “See also”