Skip to content

Roles and permissions

Every member of your organization holds one role, assigned when they’re invited, and the role decides what they can do everywhere in Ronja. The in-product Role guide puts it in one line: “Pick the role that matches what someone actually needs — you can change it later.”

This page explains the roles. Every action, role by role, is in the roles matrix.

Role What it is for
Super Admin The organization’s owner, assigned automatically to whoever creates it. Has every permission, and a few only it holds.
Admin Runs the organization day to day: invites members and assigns roles, manages access groups, settings and guests, and owns the data layer.
User Everyday use: chats with Ronja, creates features (private until shared), and proposes changes to shared resources through drafts and proposals.
User Read-Only View-only access for stakeholders: browses shared content and the member directory, and chats with Ronja about the data they can already see. Changes nothing shared.
App User Apps only: opens just the apps an Admin lists for them, from Your apps, and nothing else in Ronja. No chat with Ronja, and no features, tables, notes or files. See Give people access to apps only.

An Admin’s data-layer work covers connecting data sources, building and editing tables and setting up automations. An Admin is also the approver for governance requests: handovers, edit drafts, and note, workflow and app proposals. A maintainer of a feature decides that feature’s drafts and proposals too.

Admins see everything in the organization, whatever their access groups: every organization feature, and every member’s private features and My Private Feature, with everything in them. It shows in the admin area’s lists and Trash, in pickers and search (⌘K), in the API and the CLI, and they can open it. An Admin can also open any member’s chat for support and governance, but search finds only the chats they could open from their own sidebar (Privacy and sharing).

In pickers, in search and on the feature’s page, a colleague’s private feature carries the owner’s name, so it is never mistaken for the Admin’s own: “Anna Berg’s private feature” for her My Private Feature, “Q3 forecast (Anna Berg)” for any other.

Seeing is not changing. In a member’s private feature an Admin can:

  • edit, retire or delete a table, note, secret, workflow, app, MCP server, automation or Saved Agent that is already there, so a broken thing is fixed without taking the feature away from its owner;
  • restore, or permanently delete, what the member put in the Trash, without the owner being told;
  • attach an item from it to a shared app, or reference it from a Saved Agent, automation or workflow, which makes its contents readable through that resource. An item in the Trash can’t be attached, and a table in a feature in the Trash can’t be attached or referenced by anyone;
  • move things into it from an organization feature;
  • rename, delete, export or share the private feature itself, except a My Private Feature, which can’t be shared. When an Admin shares it, the owner gets a notification naming them and any reason they gave, and becomes its maintainer. A feature in the Trash, or an owner who has left the organization, gets neither.

An Admin can’t create anything new inside a member’s private feature, and nobody can move something between two people’s private features.

Ronja’s chat, and AI assistants connected to Ronja, find what a member would, plus the feature you open the chat in and anything you link them to. The admin area, search (⌘K) and the API you call yourself show everything, apart from members’ chats in search.

No screen, list or export ever shows a secret’s value, to an Admin or anyone. Anyone who may write code that uses a secret can make that code reveal it.

A Super Admin has every Admin permission, plus:

A Super Admin can also change the role of, or remove, anyone. Build mode and the choice of model can’t be turned off for a Super Admin on the Control Center.

A User Read-Only member holds their own chats with Ronja, and takes part in any chat shared with them with Full access. That includes their chats from Slack and Teams.

In those chats Ronja can query, chart and run Python over the data the member can already see, run a Deep analysis, read files they attach, and update Your policy for them. She can make documents and files for them, which always go to their private My Files; what the chat produces along the way follows the chat.

She can read from an external database the organization has connected, handling the credential herself; the member never sees a credential’s value. On some engines the connected account is the only thing that stops writing, so connect a read-only account.

A read-only chat can’t use Build mode, create or change anything shared (a table, note, workflow, app or automation), move, rename or share a file, send email, or change the Organization policy.

A read-only member can also:

  • share their own chats with colleagues, and comment on answers in any chat they can read. A colleague who opens a shared chat sees what Ronja said in it, excerpts of data included, but can’t open the files in the member’s My Files;
  • run their own projects: create them and file their own chats in;
  • pick the model and effort for a chat, under the same Control Center rules as everyone else;
  • contact support from Help & Support.

Read-only chats spend credits like any other, and the Control Center’s limits apply to them; see Govern AI spend.

  • An invite names the role. The Invite users dialog’s Role is User Read-Only unless you pick another, and you can change it later, before or after they accept.
  • You hand out only roles below your own. An Admin assigns User, User Read-Only or App User; only a Super Admin can make someone Admin or Super Admin.
  • Making someone an App User takes chat, files and data away. Ronja asks first, and says that the automations they own keep running. Giving an App User another role takes them off every app’s App User list.
  • You change or remove only people below your own role. An Admin can’t change another Admin’s or a Super Admin’s role, or remove them. The one exception is for removal: any Admin can remove Ronja staff, whatever their role.
  • You can’t demote yourself into a locked-out organization. Ronja refuses a self-demotion when you’re the only member at your level or above: promote someone else first.
  • The organization always keeps a Super Admin. Nobody can demote or remove its last Super Admin; make someone else Super Admin first.
  • “No role” is a real state. A member or API token without a role fails every permission check until one is assigned.

A member of the Ronja team sometimes joins your organization to help, during onboarding or to look into something you asked about. They add themselves as Super Admin from Ronja’s own tools and give a reason; someone from Ronja who is already a member can raise themselves to Super Admin the same way. No role in your organization can do this for them.

  • Your admins are told. Each of your own Super Admins and Admins (Ronja staff are left out) gets a notification under Notifications in the sidebar, titled with their name and “from the Ronja team is now a Super Admin”. It gives their previous role, if any, and their reason, opens their page on Users & Access, and appears whatever your notification settings say.
  • They are emailed too, with a Review them in Users & Access link. Until an Admin sets up routing it goes to your Super Admins and Admins, never to Ronja staff. The Ronja staff joined as Super Admin row, in the Members & access group on Notification routing, sends it to other people or to Slack, or turns it off. A person in your organization it is sent to also gets the notification in Ronja, and turning it off stops the email or Slack message only.
  • They are marked with a Ronja staff chip on Users & Access.
  • Any Admin can remove them: open them on Users & Access and select Remove from organization. If they are your only Super Admin, the notification says so, and nobody can remove them until one of you is made Super Admin, which only a Super Admin can do.
  • Removing them doesn’t stop them adding themselves again, and your admins are notified each time.

A role says what someone may do; for members other than App Users, access group membership and a feature’s scope say what they can see. A User who isn’t in the Finance access group won’t see a feature shared only with Finance (attached to that group alone, while the Default access group isn’t set to share all features), or a colleague’s private feature. Admins are the exception, as above. An App User can’t be in an access group: they see only the apps listed for them.

You assign roles on the Users & Access page, which has a role control on each member’s row. Its Role guide button opens “What each role can do”, a summary of the roles to compare before picking one.

The Role guide modal showing what each of the five roles can do The Role guide on the Users & Access page.

For the steps, see Manage users and roles.