Grant a maintainer
A maintainer is a person, or every member of an access group, whom an Admin has put in charge of one organization-scoped feature. They get full access to that feature: they see everything in it, build in it and decide its reviews as an Admin would, with the exceptions below. Everywhere else, nothing changes for them.
A grant to a person works wherever the feature lives, even in a Space they are not in. The feature is listed for them in its own Space, like everything else. If they are not in that Space, they open it from a link; include them in the Space to have it listed. A grant to an access group works only for the group’s members who are in the group’s Space, as everything shared with an access group does.
A private feature’s owner becomes its maintainer automatically when the feature is shared with the organization, so they keep full access even while no access group reaches it; see Share and promote. That doesn’t happen for a feature in the Trash when it is shared, or for an owner who has left the organization. You revoke it like any other maintainer access.
What a maintainer can do
Section titled “What a maintainer can do”- See and open everything in the feature, on its page and over the API by the feature’s id, including items an access group restricts, and even when no access group of theirs shares the feature. Search and chats with Ronja find it where the feature is listed: its own Space, or a Space it is shared into. A secret’s value stays hidden, as it does from everyone.
- Create, edit and delete everything inside it: tables and their data and health checks, apps, workflows, notes, secrets, automations, Saved Agents (a colleague’s too), MCP servers, codexes and modules. Rename the feature or change its description, and archive its items or restore them from the feature’s Trash.
- Create resources there that go live at once instead of becoming proposals. Modules are the exception: in a shared feature every new module starts as a proposal, an Admin’s or a maintainer’s included, and an Admin or a maintainer of the feature other than its author approves it.
- Decide the feature’s reviews: approve or reject colleagues’ proposals, and commit or reject their drafts once submitted.
Their own edits follow your organization’s rules like anyone else’s:
- Where your organization disallows self-approval, a maintainer’s own edits, in a chat too, go to review and someone else decides them.
- A maintainer’s edit to a Saved Agent always starts a draft, which they then commit.
- In a chat, Ronja applies a maintainer’s edit to a table directly. Over the API or the CLI they edit it through a draft and commit it.
The grant covers that feature only, not the features nested under it, and it is used only when the maintainer acts themselves: an automation never writes with it. A User Read-Only member made a maintainer sees everything in the feature, but changes and decides nothing.
What a maintainer sees only because they maintain the feature, they can use only inside it. Connecting such an item to an app, workflow, note, Saved Agent, Derived table or metric in another feature is refused, as is capturing such an item into a blueprint; Ronja names the item. To use it elsewhere, an Admin shares it with an access group they belong to.
When a maintainer talks to Ronja in a shared Slack or Teams channel, Ronja’s answers are shown to the whole channel, including what the maintainer can see in their feature.
Maintainers are also among the people responsible for the feature’s alerts: by default they are emailed when one of its workflows fails, one of its tables stops updating or a health check on one of its tables fails; see Who is told.
What stays with an Admin
Section titled “What stays with an Admin”- Changing the feature’s scope; moving, deleting, restoring or exporting the feature; making anyone a maintainer.
- Permanently deleting an item before its 30 days in the Trash are up.
- Overriding a column’s personal-data flag; verifying or retiring a table; making a health check admin-protected, or silencing or removing one that is.
- Opening one of the feature’s Email-triggered automations to any sender, or widening one that is open.
- Pushing files into an integration table.
- Scheduled imports and the Connections page, managed databases and mailboxes, and the organization-wide admin pages.
- A delete that reaches outside the feature: if removing something would take resources in another feature with it, even one they also maintain, Ronja refuses, names them, and the delete needs an Admin.
The roles matrix has every action, and Scopes and sharing shows where maintainers fit.
Where a maintainer finds reviews
Section titled “Where a maintainer finds reviews”When something in the feature is waiting for a decision, the top of the feature’s page shows a waiting for review chip with the count, for example 2 waiting for review. Clicking it opens the feature’s Inbox on the page, with the same review controls an Admin gets. The chip and the feature’s Inbox show its reviews whichever Space you are in, so a feature opened from a link in another Space still shows what is waiting. Review on the item’s own page and the draft banners offer the same decisions; no chat with Ronja approves a proposal.
Saved Agent and module reviews are listed there but decided over the API, or for a module change with the CLI; see Propose and review changes. Let your maintainers know where to look.
Grant maintainer access
Section titled “Grant maintainer access”- Open the feature and choose More → Access at the top of the page. (You can also choose More → Settings, then scroll to Access.)
- Under Add maintainer, choose Person or Access group.
- Pick them from the list: Choose a person lists the members of your organization, Choose an access group your access groups.
- Click Add maintainer.
- If the access group contains every member of your organization, Ronja says how many people that is. Click Make everyone a maintainer to go ahead.
The feature must be organization-scoped and not in the Trash. On a private feature, the Access section says maintainers apply to organization-scoped features only and offers nothing to add. A project’s feature has no Access section: it can’t have maintainers. An access group’s grant covers everyone in it, including people added later. Adding someone who is already a maintainer changes nothing.
See who maintains a feature
Section titled “See who maintains a feature”The Access section lists every maintainer: the person or access group, who granted it and when. An Admin sees it on every feature; a maintainer sees it, read-only, on the feature they maintain. Everyone else sees a short note instead.
A row marked Inactive does nothing right now: the person is no longer a member, the feature was made private or moved to the Trash, or the access group was deleted. Remove it, or undo what changed. Removing someone from your organization now ends their grants, so a former member’s row dates from an earlier removal.
See every maintainer at once
Section titled “See every maintainer at once”- On Shared features, select Browse to see the maintainers, people or access groups, beside each feature’s name and purpose. No maintainer means no grant is active; open the feature’s settings to see inactive grants.
- Maintained by, beside the name and Tag filters, narrows the list to the features one person or access group maintains, or to No maintainer. A person’s choice includes the features they maintain through an access group. Anyone clears that filter, and Clear filters resets them all.
- On Users & Access, a person’s Settings has a Maintains section listing every feature they maintain, once each, and how they hold it: directly, via an access group’s name, or both. A feature where none of their grants is active is greyed out and marked Inactive, and one in the Trash is marked In the trash and not linked. Someone with no grants shows “Not a maintainer of any feature.”
Revoke maintainer access
Section titled “Revoke maintainer access”Click Remove on the maintainer’s row. It applies from their next change, and it doesn’t undo what they built or connected while they held it.
Use the API
Section titled “Use the API”Listing and revoking maintainers can be scripted, and so can reading every grant in your organization. Granting needs a person signed in to Ronja: the CLI, API tokens, automations and Ronja herself are refused. The routes and fields are in Maintainers in the API reference.
Related
Section titled “Related”- Propose and review changes: the draft and proposal flow a maintainer decides for their feature.
- Scopes and sharing: organization-scoped features, and who decides what about them.