Skip to content
Docs · Roles and permissions

Team and roles

Roles and permissions

Yomenie has three roles: owner, admin and member. Each is a set of actions, checked by the server on every change. Here's what each role can do.

Updated

On this page

Everyone in a workspace has one role: owner, admin or member. A role is a bundle of actions, and the server checks the action on every change, whatever the app shows. Reading is open to every member, except agent keys and the audit log.

What each role can do

Chat, the floor and your own desk need no special permission: everyone can use them.

Action Owner Admin Member
Create, edit and move tickets Yes Yes Yes
See everyone’s email on the Team page Yes Yes
Make join links that work without approval Yes Yes
Remove people Yes Yes
Change roles between member and admin Yes Yes
Grant or take away the owner role Yes
Change workspace settings (the invite policy) Yes
Change room settings Yes Yes
Release or assign desks other people hold Yes Yes
Create, rename, move and archive boards Yes Yes
Create, rename and delete teams, and choose who is on them Yes Yes Join or leave a team themselves
Add agents Yes Yes
Manage an agent: edit, pause, resume, keys Yes Yes Their own agents
Change what agents may access: scopes, grants, deny rules Yes Yes
Decide approvals Yes Yes For their own agents
Manage connections Yes Yes
Read the audit log Yes Yes

“Their own agents” means agents the member manages. A manager can pause their agent, manage its keys and decide its approvals, but can’t widen its access: only owners and admins change scopes, grants and deny rules.

When you try something your role doesn’t allow, the server refuses with a plain reason, like “Only owners and admins can manage connections”.

Guard rails

  • Only owners make someone an owner or take the role away.
  • A workspace always keeps at least one owner. “The workspace needs at least one owner. Make someone else an owner first.”
  • You can’t change your own role, except that an owner can step down.

Confirm it’s you

The most sensitive changes also ask you to confirm it’s you with a passkey or an email link, even when your role allows them: connections, agent keys, agent scopes, grants and deny rules. See step-up.

Apps connected through the MCP server get only a slice of your role: they can work with tickets, and never do any of the owner- and admin-level actions above.

Custom roles and guests aren’t built yet. Coming: Custom roles and guests, on the roadmap