Resource types
Everything you build in Ronja lives inside a feature, and a resource’s audience follows its feature’s scope. Most resources are created by asking Ronja in chat — there is no create form for them in the UI.
| Resource | Where it lives | How it’s created | Scopes | Who approves sharing / changes |
|---|---|---|---|---|
| Table | A feature | Ask Ronja (Build mode), a connection sync, or a file upload in chat | Follows the feature: Private / Organization | Shared-table edits go through draft review — an Admin commits them |
| File | In Files, organized in folders — your uploads land in My Files (private by default); workflow outputs land in the shared folders their workflow files them into | Upload in chat, or produced by workflow runs | Private in My Files, or shared through a folder’s read/write access | Admins manage folder access; a workflow’s folder-write access is approved in the draft review dialog’s Access changes section |
| Workflow | A feature | Ask Ronja in Build mode only | Follows the feature | Admin (proposals and submitted drafts) |
| Note (Skill / Knowledge) | A feature | Ask Ronja only — no “New note” button exists | Follows the feature | Admin |
| Secret | A feature | Only through chat (secure credential cards); values are never displayed | Personal / Shared, derived from the feature’s scope | Creating in a shared feature requires Admin; sharing happens at the feature level |
| MCP server | A feature | Only through chat — no “Add MCP server” form | Personal / Shared, derived from the feature’s scope | Sharing follows the feature; deleting a shared MCP server requires Admin |
| Automation | A feature | Ask Ronja in an exploration (no create button in the UI) | Follows the feature | Creating in a shared feature requires Admin; no draft lifecycle |
| App | A feature | Ask Ronja in Build mode only | Shared / personal, derived from the feature’s scope | Admin only — for both new-app proposals and edit drafts on shared apps |
| Saved Agent | A feature | Ask Ronja in a conversation; the Agents pages are read-only viewers | Follows the feature | Admin approves proposals and drafts — in chat or over the API, not in the Inbox |
| Codex | A feature | Ask Ronja in Build mode; documents can also be added by workflows and apps | Follows the feature | Creating or changing one in a shared feature requires Admin; no draft or proposal lifecycle |
- Sharing is feature-based. There is no per-resource access list — a resource is visible to exactly the people who can reach its feature. To share one resource, promote its feature or move the resource into a shared feature. See Share and promote.
- Non-admin edits to shared resources become drafts. The live version keeps serving everyone until a reviewer approves. See Versions, drafts, and approvals.
- Non-admin creations in shared features become proposals, reviewed in the admin Inbox on the Shared features page.
- Deleting any of these moves it to the 30-day trash; deletion is blocked while other resources structurally depend on it.