Features

If you remember one organizing idea in Ronja, make it this: everything lives in a feature.

A feature is a named bundle of resources — tables, workflows, notes, and more — that together deliver one outcome. Think “Sales Intelligence”, “Customer Health”, or “Onboarding Funnel”: not a folder of files, but a working capability your team can use, share, and improve.

Why features exist

They’re the unit of building. When Ronja creates something durable — a table, a workflow, a data app — it lands inside a feature. The feature hub shows everything the bundle contains, grouped by kind. See The resource types for the full map.

They’re the unit of access and sharing. Features carry a scope — Private, Workspace, or Organization — and who can see a resource is decided by whether they can reach its feature through their workspaces. You never share a single table with a colleague; you share the feature it belongs to.

They’re context for the agent. The Explore button on any feature starts a new exploration scoped to it, and a feature’s description is, in the product’s own words, “Shown in listings and used by the agent when choosing which feature to use.” A well-described feature makes Ronja smarter.

Anatomy of a feature

Open a feature and you land on its hub: a hero with the name, scope pill, and kind; then three tabs — Inventory (every resource, filterable by kind), Activity (the audit feed), and File outputs (files produced by workflow runs). A Data Explorer toggle swaps the body for a table browser, and each feature has its own Trash drawer (on shared features, visible to admins) for restoring recently deleted items.

The feature hub — one page showing everything a feature contains.

Features have a kind describing their shape: Integration, Report, Pipeline, or Database (a fifth, “Connection”, is set automatically when a connector creates the feature).

See how everything connects

The feature hero has a Graph action that opens a cross-feature dependency graph for the whole feature. It lays out how the feature’s resources — its tables, workflows, automations, notes, and data apps — relate to one another, and it doesn’t stop at the feature’s edge: dependencies that reach into other features are drawn too, so you can see the real shape of the work rather than one feature in isolation. (From any resource row in the Inventory, “View in graph” opens the same graph focused on that one resource.)

The Graph action shows how a feature’s resources connect — including edges that cross into other features.

The scope lifecycle

Features are born small and grow deliberately:

1. Private — only you can see it. This is where you draft.
2. Workspace — handed over to a team. A workspace admin approves the handover.
3. Organization — the org-wide catalog. A Data Admin approves.

Moving up is a request, not an act: click Share (or Request promotion in settings), and an amber “Share pending” pill marks the feature until an admin decides. You can withdraw a pending request at any time. Moving down — including “Hand back to creator” — is admin-only and goes through the same staged flow.

Note

Organization scope doesn’t mean “visible to everyone” — an org feature still has to be attached to workspaces before anyone sees it. See Scopes and sharing.

Creating features

Members create private features by describing them. On your Features page, “New private feature” asks one question — “What do you want to build?” — then opens an exploration where Ronja creates the feature and starts building inside it. You can name it yourself or let Ronja pick the name.

Data Admins (and Admins) can also create shared features directly: New Feature on the Shared features page creates one at organization scope — “visible to any workspace you attach it to.”

Where you’ll find them

Two pages share a similar name, so note the difference: Features in the member sidebar is your home — Private and Shared lanes of the features you can reach. Shared features is the admin console — the org-wide catalog, the approval Inbox, and the Features × workspaces map.

Lifecycle and safety nets

Deleting a feature moves it to the trash, restorable for 30 days before permanent purge — see Restore from trash. A feature can also be exported as a zip of its contents from settings; secret values are never included in exports.

For day-to-day housekeeping — renaming, moving resources between features, archiving — see Organize features.