User roles and permissions in Maven

User permissions define the level of Maven access a user in your organization will have. Usually, permissions are based on a user’s role, though organization-level permissions.

The person who sets user permissions is the Admin or Owner. The Admin is the first user of any Maven organization, and each organization must have at least one Admin (any Admin can designate other users as Admins as well). When new users are invited to an organization, they are assigned the role set during the invitation process.

User roles and permissions

RolePermissions
Reader
Recommended role for third parties and agents, if you do not want them creating content or modifying the AI agents.
- View Insights
- View Knowledge
- View Actions
- View Triggers
- View Agent settings
- View Test suites
- View Conversations
- View Events
- View Users
- View Members
Admin
The highest-level permissions set in an organization. We recommend limiting the number of users in an organization who are Admins. The Admin role can only be granted or revoked by existing Admins.
- View Insights
- Resolve / Ignore Inbox items
- Add / Update / Deactivate Knowledge
- Update / Deactivate Actions
- Deactivate Triggers
- Browse / Install Apps
- Edit Agent settings
- Run Test suites
- Access Simulator
- View Conversations
- View Events
- View Users
- Edit Members
Owner
The highest-level permissions set in an organization. Owners are usually points of contact for the organization.
- View Insights
- Resolve / Ignore Inbox items
- Add / Update / Deactivate Knowledge
- Update / Deactivate Actions
- Deactivate Triggers
- Browse / Install Apps
- Edit Agent settings
- Run Test suites
- Access Simulator
- View Conversations
- View Events
- View Users
- Edit Members