Manage users and roles

Who can do this

Admin. Promoting someone to Admin or Super Admin requires the Super Admin.

User management lives on Users & Access in the admin area: a matrix with one row per member and one column per access group. Each cell shows whether that person is a member of that access group — so the whole access picture fits on one screen. Find people with the search box (“Search by name or email”) and the Role and Status filters.

The Users × Access Groups matrix — people, roles, and access group membership in one view.

Invite members

1. Click Invite users.
2. Type email addresses in the Send invite modal — a comma or Enter turns each into a chip.
3. Click Send invite (or Send N invites). Each person receives an invitation email and appears in the matrix with an amber Invited chip until their first login.

Note

Invited users start as User Read-Only — the least-privileged role. Set their real role right away (next section); you don’t have to wait for them to accept.

Hover an Invited row to reveal Resend invite.

Assign roles

Click a row’s role pill and pick from the list. The five roles are explained in Roles and permissions, and the exact capability table is in the roles matrix — the Role guide button on this page opens the same overview in-product (“What each role can do”).

Two guardrails:

• An Admin can only hand out roles below their own level — User, User Read-Only. Only the Super Admin can make someone Admin or Super Admin.
• You can’t demote yourself if you’re the only person at your level or higher: “Promote another teammate to at least {role} first, then change your own role.”

Read-only members and Ronja’s AI

The Read-only members can use Ronja’s AI toggle at the top of this page decides whether members on the User Read-Only role can hold their own conversations with Ronja. It’s on by default, and it applies to the whole organization — including when a read-only member asks Ronja from Slack or Teams.

A read-only conversation is read-and-analyze only: Ronja can query, chart and run Python over data that member can already see, and the results stay in the chat. It can’t create or change a shared table, note, workflow, app or automation, and it can’t send email.

Stored credentials stay out of their hands in the sense that matters: a read-only member never sees a credential’s value, and can’t put one into code they wrote. They can ask Ronja to read from an external database the organization has connected — read-only, and Ronja handles the credential itself.

Read-only chats spend credits like any other conversation. The per-role budgets in Govern AI spend apply to them — set a budget for User Read-Only if you want a cap that’s separate from the rest of the organization.

Grant access group access

1. Click the cell where a user’s row meets an access group column.
2. Confirm the change. Adding: “{user} will be able to see and use everything {access group} has access to.” Removing: “{user} will lose access to {access group} and everything inside it.” Both are undoable from the matrix.
3. Use the EVERYONE IS A MEMBER toggle row above the user rows to open an access group to everybody — every current and future member of the organization joins automatically (“New hires get access without an extra invite step.”), and the column’s cells lock while it’s on.

You cannot remove yourself from an access group — ask another admin.

Work in bulk

Select rows with the checkboxes and a bottom bar appears: Add to access group, Remove from access group, and Change role. Your own row is skipped for removals, and bulk role changes refuse to include you — change your own role from the per-row pill.

Edit one user

Open a row’s Settings link for the user drawer: edit the first and last name, change the role (including removing it — a member with No role can’t do anything until one is assigned), review the user’s audit Activity, or Delete user.

Caution

Delete user is permanent: “Delete user {name} ({email}). This action cannot be undone.”