Organize features

Who can do this

Any member can rename features they can edit and request moves. A move between two of your own private features executes instantly; moves involving shared features need an admin’s approval.

Once you have features, you’ll want to keep them tidy — rename them, move resources between them, and archive what Ronja should ignore. Here’s how each works.

Rename a feature

1. Open the feature and click Settings.
2. Edit Name — “The display name used throughout the application.”
3. Click Save.

A feature’s name has to be unique, and the database enforces it as well as the app does — so it holds no matter which way the feature was created. For a feature the whole organization can see, that means unique across the organization; for a private feature, unique among your own — two people can each have a private feature called Sales. Capitalization and spaces around the name don’t make it a different name, so Sales and sales are the same name. If the one you typed is already in use, Ronja says so under the field and names the feature that has it, and your typing stays put so you can adjust it.

A feature you put in the trash gives its name up right away, so something else can take it while it is in there.

A name you type here also has to work as a handle: no full stop, no double quote, no @, not all digits, and not something shaped like one of Ronja’s internal ids. This is a rule about the new name only. A feature created by a connector or over the API can carry a name the rename form would not accept — Sales.EU, say, with a full stop in it — and it keeps working; you can rename it to anything that follows the rule, and nothing forces you to. Keep the description fresh too — it’s “shown in listings and used by the agent when choosing which feature to use.” You can also edit the description directly on the feature page: click it, type, then press ⌘↵ to save.

Move resources between features

Moves run through a governed flow: you pick the items, Ronja computes what has to ride along, and shared destinations require approval.

1. On the feature page, click Select.
2. Tick the resources to move.
3. Click Move N resource(s).
4. Pick the destination under Move to — each candidate shows its scope badge.
5. Review Resources to move: your own picks are tagged “selected” and locked; auto-added dependencies are tagged “linked” and can be unticked.
6. Fill in Rationale if the move needs approval.
7. Click Move now (instant or self-approved) or Submit for approval.

The banner above the list tells you which path you’re on: “Both features are private — this move executes immediately.” or “This move requires approval from an organization admin.”

As an Admin, Move to also offers your colleagues’ private features, each shown with its owner’s name — for example “Q3 forecast (Anna Berg)” — when you move from an organization feature. Nobody can move something between two people’s private features, so when you move out of a private feature the list offers the organization’s features and only that feature’s owner’s other private features.

Caution

While a move awaits approval, the bundled resources are claimed — they can’t join another move, and a scope change on the target feature can’t be approved until it’s decided. The approver can exclude “linked” items but never your selected seeds. Withdraw a pending move from Account → Requests if you change your mind.

Favorites

The sidebar’s Favorites section keeps your most-used items one click away — up to 10 per type in each Space.

Tags

To group related work that spans several features — every “finance” table, everything for a launch — label resources with colored tags instead of moving them. Tags are organization-wide (in the Space you’re in, if your organization has more than one), searchable in ⌘K, and filter the Shared features grid.

Archive what’s no longer relevant

Archiving removes a resource from Ronja’s sight without deleting anything — “The agent will no longer see this…” — and it’s fully reversible.

1. On the feature page, switch the section’s filter chips — Live | Archived (tables show Visible | Hidden | Archived) — to see both sets.
2. Click Archive on the row, or select several rows and archive them in bulk.
3. Click Unarchive any time to bring one back.

An archived item’s name is free while it’s away, so something else can take it. If that happened, the item comes back under a slightly different name — its own name with a short code after it, like Orders (k3m9pq) — rather than refusing to come back at all. Rename it to whatever you want once it’s live again.

Archiving a table a workflow writes to doesn’t stop the workflow: it keeps writing the table while the table is archived. To stop the writes, change the workflow or archive it.

If other resources structurally depend on the item, the Archive button stays disabled until they’re untangled — click Untangle in exploration → and Ronja rewrites the dependents for you.

Archiving is not deleting: deleted items go to the trash and can be restored for 30 days — see Restore from trash.