Monitor activity and usage

The Activity page shows how your organization uses Ronja: who uses it and whether that is growing, what people work on, where they get stuck, which apps they open, which tables they rely on, and what Ronja built from their chats. Open it from the admin sidebar: Activity → Overview. It has five tabs — Overview, People, Topics, Apps and Data — and shows usage only, never credits (see Where spend lives).

The time window

The 7 d · 30 d · 90 d toggle at the top picks the period the counts cover: the last 7, 30 or 90 days. The page opens on 30 d. The window changes counts, never a person’s status.

Weekly charts always show the last 12 weeks, and every 8 weeks column the last eight of them, whatever the window. A week runs Monday to Sunday (UTC). A chart draws as soon as any week has something in it, even a single week, and a full chart shows its first and last week’s dates under it; hover a column to see that week. The Topics and Data side panels name both periods: the counts under the panel’s title cover the window (“in the last 30 days”), and its weekly chart says “last 12 weeks”.

Each tab, and each row’s side panel, has its own address, so you can bookmark a view or send it to another admin.

Who counts

Only the organization’s current members count. Saved Agents, automations, API tokens and people who have left never appear in People and never add to a count of people. Where the page says “N of M people”, M is the members who have signed in: people with a pending invite are listed, but not counted in M.

A person is seen when they use Ronja in this organization — in the browser with the tab in the foreground, or through a connected Slack or Teams channel. Activity in another organization they also belong to does not count, and neither does a tab left open in the background.

A chat counts once Ronja has read it and given it a theme, which happens after the chat has gone quiet. Automation runs are never counted as chats.

Overview

Six short sections, each with a link to the tab that has the detail:

Needs a look — up to five things worth your attention, or “Nothing needs a look right now.”:
- Slipping: someone who used Ronja every week for four weeks and has not been seen for 8 to 30 days.
- Stuck: a topic with at least 4 chats where a quarter or more ended stuck or abandoned.
- Invite: people invited who have not signed in yet.
- Unopened: published apps nobody opened in the window.
Each row’s Open takes you to the person, topic or list that explains it.
Who is using Ronja — “N of M people active in the last 7 days”, a line counting each status, and a chart of the people active each week over the last 12 weeks, split into Returning and New.
Where people get stuck — the topics with the largest share of chats that ended stuck or abandoned, and how many chats were marked “not happy with this response”.
What people work on — the six busiest topics, with their chats, people, an 8-week trend, and how their chats ended: Completed, Exploratory, Stuck or abandoned or Unclear.
Apps in use — how many people opened an app, the three apps with the most viewers and their reach, and how many published apps nobody opened.
Data in use — how many tables were read, the three most-read tables with their reads and readers, and how many tables nobody looked at. Under it, Built from chats counts what Ronja built in chats, by kind.

People

One row per member: Person, Status, Last seen, Active days, 8 weeks (one square per week, filled when the person was seen), Chats, Completed (the share of their chats that ended completed), Top topic and Built.

Each person has one status, and it does not change with the window:

Status	Means
Active	Seen in the last 7 days
Slipping	Last seen 8 to 30 days ago
Dormant	Last seen more than 30 days ago
No recent activity	Has signed in, but has not been seen in this organization in the past year. Someone who works with Ronja only through an API token reads this way
Invited	Invited, and has never signed in

A New badge marks someone first seen in the last 14 days.

Click a name to open the side panel: when they were first and last seen, active days, apps opened and tables read; their topics; how their chats ended; what Ronja built from their chats; and the chats themselves. A link to someone who has left the organization opens a panel that says “Not a current member.”

Topics

Ronja files each chat under one topic: an area of your business, named in a few words, never after a person, a single event or a date. A chat that continues keeps its topic. The organization has at most 40 topics in use at a time; past that, a new subject is filed under Other. Chats Ronja has not filed yet are listed together as Not yet sorted, at the bottom of the list, and the line under the table says how many there are.

The columns are Topic, Chats, People, 8 weeks, Completed, Stuck (chats that ended stuck or abandoned) and Not happy (chats with a “not happy with this response” mark).

Click a topic to open its side panel: its description, Chats per week, last 12 weeks, Outcomes with how the chats felt (Satisfied, Neutral, Frustrated, Unclear), the People who worked on it, the Features and Data its chats used, and its Chats.

Chat lists

The Chats list in a person’s or a topic’s panel shows each chat’s theme, a short summary Ronja wrote, how it ended, the date and an Open link, 50 at a time — Show more chats loads the next 50.

Apps

The line at the top reads “N of M people opened an app”, then how many people used apps but started no chats in this window, and how many published apps were never opened. All apps / Never opened narrows the list to the published apps nobody opened in the window; when no app is published, it says “No published apps yet.”

The columns are App, Feature, Built by, Viewers, Reach (viewers out of the members who have signed in), 8 weeks, Opens and Last opened. Opens count people opening the published app; an author’s previews of a draft do not count. An app opened in the window that is no longer published is still listed, marked Not published.

Click an app to open its side panel: who built it and when it was last published, Open app, Viewers per week, last 12 weeks, and the Viewers, each with their opens and when they last opened it. Click a viewer to see them on People.

Data

The line at the top counts the tables read in the window and the tables nobody looked at in it; open in Data map shows those on the Data map’s Usage lens. “Read” means a recorded query — opening a table’s page records nothing.

The list starts with the 50 most-read tables, most read first; Show up to 200 tables, then 500, extends it. The columns are Table, Kind, People, Reads, 8 weeks, Via, Apps using it (the published apps allowed to read the table) and Last read. A metric can appear too: working one out counts as a read of the metric.

Via says how the table was read. Each read counts once:

apps — a read made for an app, whoever opened it.
workflows — a workflow run a person started.
chats — a person reading, in a chat or directly. A chat’s reads count for the person who ran it, so reading in a colleague’s shared chat counts for you.
other — API tokens, Saved Agents and automation chats, plus app reads from before Ronja began recording which app made them.

Click a table to open its side panel: Open table, Reads per week, last 12 weeks, its Readers (people link to People, apps to Apps, and a Saved Agent is marked Saved agent), and the Apps using it.

Built from chats

Built from chats (on the Overview, and per person under Built) counts what Ronja created inside a chat and still exists: apps, workflows, automations, tables, metrics, Saved Agents and shared modules. An app counts once published; a workflow, Saved Agent or module once committed; a table only when it belongs to a feature, so a chat’s scratch tables do not count. Anything archived, in the Trash or deleted drops out, and a renamed item shows its new name.

Where spend lives

Activity shows usage, never credits. Admins whose organization has billing access see a Spend link at the top of the page, which opens the Control Center. Credit breakdowns by person, model and mode are on the Usage page (Usage & billing), and the wallet balance is on the Super Admin’s Billing page.

The rest of the Activity group — Runs & Traces and the Audit log — is covered in Activity log.