The agent

Ronja is two things: the product where your data lives, and the agent you talk to. This page is about the agent — the assistant who answers questions about your data, analyzes it, and, when you ask, builds things your whole team can keep using.

Where you meet her

You work with Ronja in explorations — conversations where you ask questions in plain language. A fresh exploration greets you with “Let’s start analyzing” and a few example prompts; from there, you just type. Everything Ronja can reach is organized in features — named bundles of tables and related resources — and she uses them as her working context.

She shows her work

Ronja doesn’t just hand you an answer. Each reply opens with a collapsible work block — “Thought for … · N steps” — where you can see the steps she took. The answer itself arrives as prose, with tables, charts, and reference pills: inline links to the tables, workflows, and other resources she used or created. Clicking a resolved pill opens that resource in a side panel, so you can inspect it without leaving the conversation.

Three ways of working

Every exploration runs in one of three modes, chosen when you start (Build can also arrive mid-conversation — see the modes page): Standard for everyday analysis, Deep analysis for rigorous, methodology-first investigations, and Build for creating durable resources. See Standard, Deep analysis, and Build for what each unlocks and who gets Build.

You stay in control

Ronja acts autonomously for reads and analysis, but consequential actions pause for you. When she proposes a gated action, the conversation stops and a strip appears above the composer with a plain-language summary — “Send 1 email”, “Clear table” — and three choices: Reject, Approve, and Approve for session (approve this and don’t ask again for these tools in this conversation). Expand the strip to review exactly what will happen: draft changes, an email preview, or the full set of things a delete would affect.

Caution

Destructive actions spell out their consequences before you approve — for example, clearing a table warns that all rows will be permanently deleted and that this can’t be undone. Read the strip before clicking Approve.

Some gates name specific approvers. If a workflow requires sign-off from particular people, you’ll see “Awaiting approval from …” — only the named approvers can approve, though anyone can Reject.

Sometimes Ronja needs information rather than permission. In that case she presents a form to fill in, and the conversation waits until you submit it.

When she gets it wrong

Every completed assistant reply has a thumbs-down button — “Not happy with this response”. Pressing it posts a visible chip in the thread, and Ronja immediately analyzes what went wrong in the same conversation. The Ronja team is also notified, so recurring problems get fixed at the source.

Model and effort

Some users see a Model dropdown and an Effort pill (Low / Medium / High) above the composer. Availability is governed: your administrators decide who can change these, and organization policy may adjust what actually runs — you’ll see a banner such as “Running {applied model} instead of {requested model} due to company policy” when it does. See Credits and AI spend for how this is managed.

The agent is not a “Saved Agent”

One naming distinction worth learning early: “Ronja” and “the agent” always mean the assistant you chat with. A Saved Agent is a resource — a reusable prompt, model tier, and set of tool grants that you create by asking Ronja to package one, then run from other conversations or automations. See Create a saved agent.