What's the difference?

Short answers to Ronja’s most commonly confused pairs. Each section links to the full page.

Admin vs Super Admin

An Admin runs the day-to-day: inviting members, assigning roles (below their own level), managing workspaces, reviewing shared content, and restoring things from the trash. The Super Admin is the org owner — assigned automatically to whoever created the organization. Only the Super Admin can promote members to Admin or Super Admin, buy credits, register a login domain for auto-join, or delete the organization. Every organization needs at least one Super Admin, and you cannot demote yourself if you are the last one. Full details in the roles capability matrix.

Workspace vs Feature

A workspace is a container for people: members are added to workspaces, and a workspace decides which features its members can reach. A feature is a container for work: a named bundle of tables, workflows, notes, data apps, and other resources that together deliver one outcome. Data always lives in features; access always flows through workspaces. Promoting a feature to Organization scope does not automatically show it to everyone — an admin still attaches it to workspaces. See Workspaces and Features.

Note vs Knowledge

A note is a document attached to one feature, written through chat. Notes come in two kinds: Skills teach Ronja a procedure (“how we build the weekly report”), and Knowledge notes record reference facts about that feature’s data. Separately, the Knowledge page holds organization-wide knowledge — terminology, business rules, KPI definitions — that applies in every conversation, curated by admins via “Curate in chat” (there is no edit form: tell Ronja what to change). Rule of thumb: tied to one feature’s data → note; true org-wide → the Knowledge page. See How Ronja learns.

Workflow vs Automation

A workflow is a reusable job — a named, parameterized Python program Ronja writes for you, which you can run manually or reuse anywhere. An automation is a trigger paired with an action: it fires a workflow or a Saved Agent on a schedule, on an inbound email or webhook, or when a watched table rebuilds. The workflow is the work; the automation is the “when”. See Workflows and automations and the automation triggers reference.

Exploration vs Saved Agent

An exploration is a conversation: you and Ronja working through a question interactively, one session at a time. A Saved Agent is a packaged, reusable agent — a saved prompt plus model tier and tool grants — that can be invoked from any chat, tested from its own page, or run headlessly by an automation. If you find yourself giving Ronja the same instructions repeatedly, ask her to save them as a Saved Agent. See Explorations and Create a saved agent.

Connection vs MCP server vs Bridge

A connection imports data: a configured connector instance (PostgreSQL, HubSpot, …) that syncs an external system’s data into Ronja tables on a schedule. An MCP server adds tools: an external service Ronja connects to as a client, whose tools join the agent’s toolbox (it brings capabilities, not tables). A bridge adds a chat surface: it connects Ronja to a Slack or Microsoft Teams channel so your team can talk to her where they already work. See Connect a data source, Connect MCP servers, and Use Ronja in Slack and Teams.

The Usage page vs the Billing page

Two different sidebar entries under Usage & Control. Usage (page heading “Usage & billing”) is the breakdown: what drove your credit consumption this cycle — by source, user, model, and mode. It’s visible to admins whose organization has billing access enabled — ask Ronja to enable it. Billing is the wallet: the Super-Admin-only page showing total available credits, the Buy credits form, and the purchase history (“Credit extensions”). Check where credits went on Usage; top credits up on Billing. See Credits and AI spend.