Glossary

Terms as they appear in the product. Cross-references in italics point to other glossary entries.

Term	Definition
Access request	A request from someone in a bridged Slack or Microsoft Teams channel who doesn’t yet have a Ronja account and wants to join your organization. Admins approve or decline it in the Inbox.
Admin	The role that runs day-to-day administration: people, settings, workspaces, and content review. See the roles capability matrix.
Agent-visible fields	The only fields of a secret that Ronja may reference by name (for example a host or username). Sensitive values are never among them.
Allocation	A monthly per-user credit cap set in the Control Center: Limited (a credit amount), Unlimited, or Blocked. Individual exceptions override the role setting, which overrides the org default.
Allowed URLs	The list of hosts a secret or MCP server is permitted to reach — Ronja’s guardrail on where credentials can be used.
API token	An admin-created credential for calling Ronja’s API. Shown exactly once at creation; can be limited to specific scopes or given full access within its role. See the API reference.
Approve / Approve for session	The buttons on the in-chat approval strip when Ronja proposes a gated action. “Approve for session” skips re-asking for the same tools in this conversation; per-run workflow gates always re-ask.
Archive	Reversibly removing a resource from Ronja’s working view — the agent no longer sees it, but nothing is deleted. Distinct from Trash.
Ask Ronja	The home-page prompt box (“Ask anything…”). Typing a question there starts a new exploration.
Automation	A trigger paired with an action: run a workflow or Saved Agent on a schedule, on an inbound email or webhook, or when a watched table rebuilds. See the automation triggers reference.
Billing cycle	Your organization’s billing period. It runs anniversary-to-anniversary per organization, not necessarily by calendar month.
Billing page	The Super-Admin-only page showing the credit wallet, the Buy credits form, and purchase history. Not to be confused with the Usage page — see What’s the difference?.
Bridge	A connection between Ronja and one Slack or Microsoft Teams channel (or direct-message thread), letting your team talk to Ronja from chat.
Build access	The Control Center setting deciding which roles and individuals can enter Build mode.
Build mode	The exploration mode in which Ronja designs and builds durable resources — tables, workflows, data apps — writing a Plan first. Capability-gated per user.
Build (tables)	The step that turns a table’s inputs into queryable data. For the file push API, POST /build makes pushed files queryable.
Catalog	The column-statistics view on a table (Field, Kind, Rows, Missing, Cardinality, Examples).
Commit	Landing a draft onto the live version of a shared resource. Admins commit directly; others submit for review first.
Connection	A configured connector instance attached to a feature, syncing an external system’s data into tables on a schedule.
Connector	An integration type (PostgreSQL, HubSpot, SharePoint, …). Ronja has 10 native sync connectors, 28 one-click OAuth services, 8 directly queryable database engines, and an agent-driven path for effectively any HTTP API.
Control Center	The admin surface for governing AI spend: allocations, build access, spend thresholds, and model defaults. See Govern AI spend.
Credit extensions	The purchase-history table on the Billing page — every credit top-up your organization has bought.
Credit pool	The Control Center’s view of the organization’s credit allowance for the current period (“Pool consumption”, “% of pool”).
Credits	Ronja’s metering unit — all usage is “metered in credits”. See Credits and AI spend.
Curate in chat	The way org Knowledge is edited: there is no edit form — you tell Ronja what to change and she updates the knowledge (“tell, don’t edit”).
Data Admin	The role that owns the data layer: connects sources, builds tables, schedules jobs, and approves most content changes.
Data app	An interactive app Ronja builds during explorations — open it full-screen, share it with your team via its feature. See Build a data app.
Data dictionary	A table marked as the reference dictionary for a feature, linked to the data tables it describes.
Deep analysis	The rigorous, methodology-first exploration mode: Ronja designs the approach and maintains a Methodology document. Chosen on the start screen and fixed for the session.
Draft	Your private working copy of a shared resource (table, workflow, note, or data app). The live version keeps serving everyone until the draft is committed.
Editorial policy	A per-note setting for who can suggest edits: “Admins only” or “Workspace members”.
Effort	The reasoning-effort level for a chat: Low, Medium, or High. Selectable only when your admin has granted the model/effort capability and the organization’s credit wallet is funded.
Execution trace	The step-by-step timeline of a run — “What Ronja did, step by step — and where the time went.” See Monitor runs and traces.
Exploration	A conversation with Ronja — the core working surface. Private by default; shareable per person or workspace.
Favorites	Pinned explorations and data apps, shown at the top of the sidebar. Maximum 10 per type.
Feature	The central container in Ronja: a named bundle of tables, workflows, automations, notes, secrets, and apps that together deliver one outcome. See Features.
File outputs	The feature-hub tab listing files produced by workflow runs, grouped by the producing workflow.
Handover	Requesting a scope change for a feature — handing it from private to a workspace, or to the organization. An admin approves.
Inbox	The admin review queue for pending handovers, proposals, edit drafts, moves, and access requests. It lives on the Shared features page — the Governance page holds settings, not the queue.
Knowledge (note kind)	A feature-scoped reference note about that feature’s data — how a table behaves, what a metric really calculates.
Knowledge (organization)	The org-wide knowledge base Ronja consults in every conversation — terminology, business rules, KPI definitions. Browsed on the Knowledge page, curated via Curate in chat.
Manual-integration table	A table fed by files you push through the API instead of a connector. See the API reference.
MCP server	An external tool provider Ronja connects to as a client; its tools join Ronja’s toolbox. Created only through chat.
Methodology	The living research document of a Deep analysis session: goal, hypotheses, method, feasibility, and validation.
Model tier	A Saved Agent’s model class: Fast, Standard, or Mega.
Move request	A request to move resources between features. Your chosen items are seeds (locked in); auto-included dependencies are linked (can be excluded).
Note	A document attached to a feature that teaches Ronja — kind Skill (a procedure) or Knowledge (reference facts). Written through chat. See Write notes.
Organization	Your company’s Ronja account — the top-level container for all workspaces, features, and members.
Personal memory	Your private notes-to-Ronja about yourself (role, preferences, working style), editable under Account → Memory. Capped at 2,000 characters.
Plan	The implementation plan Ronja writes and maintains during a Build mode session, shown in the Plan panel.
Proposal	A brand-new shared resource awaiting approval — “proposed as a new shared workflow”. Reviewed in the Inbox.
Receiver URL	The public URL a webhook-triggered automation listens on. Treat it as a secret unless you add a signing secret.
Re-authorize	Refreshing an expired or revoked authorization (“Re-auth needed”) on a connection, integration, MCP server, or bridge.
Reduced models	The fallback model + effort set agents switch to when a spend downshift threshold fires, protecting the remaining credit pool.
Reporting timezone	The timezone reports group days, weeks, and months in — separate from when a schedule fires.
Routable address	The private email address of an email-triggered automation — mail from allowlisted senders to this address fires the automation.
Run	One execution of a workflow or agent, with a status of Running, Success, Warnings, or Failed.
Runs (panel)	The exploration side panel listing every workflow and agent run spawned in this conversation, each with its execution trace.
Saved Agent	A reusable, callable agent — a saved prompt plus model tier and tool grants — created and edited in chat, invocable from any conversation or automation.
Scope	Who can see a feature: Private (only the creator), Workspace (members of one workspace), or Organization (available to workspaces that attach it). See the scopes reference.
Search	The find-anything modal (sidebar Search or ⌘K) covering features and everything inside them.
Secret	A stored credential record. Values are entered once and never displayed anywhere in the product — not even to admins.
Self-approval	An org policy deciding whether the admin who authored a request may approve it themselves.
Setup	The guided setup wizard for new organizations; reopened from the sidebar Setup button until onboarding completes.
Signing secret	An optional HMAC secret for a webhook-triggered automation, so only signed requests can fire it. Shown once at creation.
Skill (note kind)	A note that teaches Ronja a task or procedure, loaded automatically when a relevant request comes up.
Soft limit	The credit-balance level at which Ronja warns admins and reduces model cost — without blocking work. When credits fully run out, runs are blocked until more are added.
Spend thresholds	Pool-percentage rules in the Control Center: Org warning (email admins), User warning (in-app banner), and User downshift (switch to Reduced models).
Standard (mode)	The default exploration mode for everyday analysis — ask questions, explore data, get answers.
Standard model set	The normal per-mode model + effort defaults, used unless a downshift is active.
Structural dependents	Resources with typed references to another resource; they block deleting or archiving it until untangled. Free-text mentions (“content dependents”) merely dangle.
Submit for review	The drafter’s explicit hand-off that makes a draft reviewable — an admin can only approve after it.
Super Admin	The org owner role: everything an Admin can do, plus promoting admins, buying credits, registering login domains, and deleting the organization.
Sync	One import run of a connection. Verbs on the connection page: Sync now, Stop sync, Reset.
Sync schedule	When a connection syncs: Interval (every N hours) or Cron — mutually exclusive, minimum once per hour.
Table	The data primitive. Kinds: Foundation, Integration, Derived, and Dynamic — see the table types reference.
Tangent	A private branch forked from an exploration to try something without disturbing the main thread; fold findings back with “Summarize & return”. See Tangents.
Trash	The 30-day recovery area for deleted items. Restore within 30 days, or an admin can delete permanently.
Untangle	“Untangle in exploration →” — an agent-assisted session that rewrites a resource’s dependents so it can be archived or deleted.
Up next	The single queued prompt waiting to run when Ronja finishes her current turn.
Usage page	The credit-usage breakdown (page heading “Usage & billing”) — what drove consumption this cycle, by source, user, model, and mode.
User	The everyday role: explore data, ask Ronja, upload files, create private features.
User Read-Only	The view-only role — sees shared content and the member directory, but cannot run analyses or create anything. The default role for new invitees.
View / Full access	The two exploration share modes: View (read the conversation) and Full access (can also prompt). The owner always has full access.
Wallet	Your organization’s credit balance (“Total available credits”) — credits added minus credits used.
Watched tables	The tables a Table-triggered automation monitors; it fires when any of them finishes rebuilding.
Withdraw	Cancelling your own pending request, draft, or proposal before it’s decided.
Workflow	A named, reusable, parameterized Python job Ronja writes for you — run it manually, from explorations, or via automations. See Create a workflow.
Workspace	A team space: members are added to workspaces, and workspaces decide which features those members can reach. See Workspaces.