Skip to content

Roles & Permissions

Menatic AI uses role-based access control (RBAC) to restrict what users can see and do, with permissions grouped by resource type and action.

RoleDescription
adminFull access to all resources and settings
userBasic access — read notebooks and models

You can create custom roles with any combination of permissions.

Permissions follow the pattern <resource>:<action>:

PermissionDescription
jupyter:readView all notebooks
jupyter:read_ownView only own notebooks
jupyter:writeCreate new notebooks
jupyter:deleteDelete notebooks
PermissionDescription
mcp:readView all MCP servers
mcp:writeDeploy new MCP servers
mcp:deleteDelete MCP servers
PermissionDescription
models:readView available models
models:writeAdd/configure models
models:deleteRemove models
PermissionDescription
workflows:readView workflows and builds
workflows:writeCreate and run workflows
workflows:deleteDelete workflows
PermissionDescription
settings:readView system settings
settings:writeModify system settings
  1. Go to Settings → Roles
  2. Click New Role
  3. Enter a role name
  4. Toggle individual permissions on/off
  5. Click Save

The read_own action on the jupyter resource enables object-level access control. Users with this permission can only see notebooks where they are assigned as the owner.

This is useful for:

  • Multi-tenant environments where users should not see each other’s notebooks
  • Teams where each member has their own isolated environment

To use read_own:

  1. Assign a user the role with jupyter:read_own (not jupyter:read)
  2. When creating notebooks for this user, set their account as the Owner

Roles are assigned per user in Settings → Users. A user can have one role. To combine permissions, create a custom role that includes the required permissions.