Your permissions in elvex are determined by four factors: your company-wide role, whether a resource is public or private, any specific access you've been granted to individual agents or datasources, and your membership in groups.

When you're invited to elvex, your administrator selects a role which can be a Member, Creator, or Admin. Consumer is a historical role that still exists for some users. Your role determines your permissions across elvex, but works in tandem with specific roles you may have been granted on an Agent or Datasource.

Agents and Datasources have a Visibility setting which can either be:

By default, all new Agents and Datasources have their visibility set to Private.

Groups allow you to organize users into teams and manage resource access at the group level. Instead of adding individual users to each resource, you can add them to a group and share resources with the entire group.

Users within a group can have one of three roles:

When you share a resource with a group, the group receives either:

If a user has access to a resource through both individual permissions and group membership, the highest privilege role wins.

Example:

Learn more: What are Groups and how do they work?

Modify the Visibility of the agent or datasource and set it to Public. This will effectively give all users within your company Viewer access to this agent or datasource allowing them to use it, but not modify it.

Create a group for your team, add the team members, then share the resource with the group. This is more efficient than adding users individually, especially when managing multiple resources.

Learn more: How to create and manage groups

For agents:

For datasources:

For agents, expand the Security & Permissions setting. For datasources, scroll to Permissions.

The owner of an agent or datasource is always the person that created that agent or datasource, unless ownership has been transferred to another user.

This is currently only supported via a support request to [email protected] but we'll soon allow owners to transfer ownership. Alternatively, a team member can copy the agent or datasource and make their own version.

The answer here depends on what access the user cloning the agent has to the underlying datasource. If the user has access to the datasource via Viewer, Editor or Owner roles (either individually or through a group), the cloned agent will contain a connection to the original datasource. If the user cloning the agent does not have access to the datasource, they will create an agent with identical configuration to that of the initial agent, but the cloned agent will not have access to the original datasource. The agent creator will have to request access to the datasource.

All new agents or datasources default to their visibility set to private.

For now, yes, both private and public agents still show their requests and responses in the elvex audit log. This means administrators can currently see all conversation content, even from private agents. In a subsequent release, we plan to change this behavior so that admins can see that private agent requests were made, but not see the detail of the request or response of that private agent. This is an area we're open to feedback on so if you have thoughts, please let us know at [email protected]

Yes, but with some caveats. Setting your agent's visibility to Private means that you cannot set Slack permissions to "All Slack users" as this would potentially allow non-authorized users to use your agent and its connected datasources. Private agents can only have the "Match elvex permissions" setting enabled for Slack which effectively means that you can only use Private agents via direct messages in Slack.

Yes. You can add an API user to a private agent giving that user only the ability to see that agent.

While you can assign either the Viewer or Editor role to an API user, it currently doesn't make much of a difference as API users cannot edit agents via the API.