Understanding Agent Visibility
When sharing an agent, you have three visibility options that determine who can discover and access it:
Private (default)
Only you can see and access the agent
The agent won't appear in other users' agent lists
The agent is not accessible in Slack or Microsoft Teams, even if connected
Use this for agents you're still building or that contain sensitive workflows
Private + Shared with specific individuals or groups
Only you and the people/groups you explicitly share with can access the agent
The agent appears in the agent list for everyone you've shared it with
In Slack or Microsoft Teams: Only the specific users you've shared with can access the agent
Use this when only certain teams or individuals need access (e.g., a sales team agent, an HR onboarding agent)
Public
Everyone in your organization can see and access the agent
The agent appears in all users' agent lists
In Slack or Microsoft Teams: You have the option to make it available to everyone in your organization, even if they've never logged into elvex
Use this for widely useful agents like company knowledge bases, general research assistants, or common workflow tools
Viewer vs Editor Permissions
When you share an agent with someone, you assign them one of two roles:
Viewer
Can use the agent (start conversations, ask questions, run workflows)
Can see the agent in their agent list
Can access the agent in Slack or Microsoft Teams (if connected)
Cannot modify the agent's configuration, instructions, or settings
Cannot see or edit datasources, actions, or other connected resources
Best for: End users who need to use the agent but shouldn't change how it works
Editor
Can use the agent
Can access the agent in Slack or Microsoft Teams (if connected)
Can modify the agent's configuration, instructions, and settings
Can add or remove datasources, actions, and integrations
Can change sharing settings and add/remove other users
Best for: Team members who help maintain and improve the agent
Important: Even when an agent is set to Public visibility, only users with explicit Editor permissions can modify it. All other users automatically have Viewer access.
How to Share with Specific Users or Groups
To give specific people or teams access to an agent:
Open the agent you want to share
In the configuration menu, expand the Security & Permissions section
Click the Add User or Add Group button
Search for the user or group by name or email
Select the appropriate role:
Viewer if they should only use the agent
Editor if they should be able to modify it
Click Save & Publish to confirm the changes
What happens next: The user or group members will receive an email notification and see a notification in their elvex notification feed letting them know the agent has been shared with them. The agent will immediately appear in their agent list and become accessible in any connected chat apps.
How to Make an Agent Public
To give everyone in your organization access to an agent:
Open the agent you want to share
Expand the Security & Permissions section
Locate the Visibility setting
Change the setting from Private to Public
Click Save
When you make an agent public:
All users in your company can immediately see and use the agent
The agent appears in everyone's agent list
Users have Viewer access by default (they can use but not modify the agent)
Only users you explicitly grant Editor permissions can modify the agent configuration
Option to make the agent available to all Slack or Teams users, regardless of elvex role.
Using Groups for Efficient Sharing
For easier management, we recommend sharing with Groups rather than individual users whenever possible.
Why use Groups:
Add or remove access for multiple people at once by updating the Group membership
Avoid updating permissions on every agent individually when team members change
Maintain consistent access patterns across multiple agents (e.g., "Sales Team" group gets access to all sales-related agents)
Easily control chat app access for entire departments
See How to Create and Manage Groups for more details.
Who Can Share Agents
Sharing is not available for users with Member or Consumer roles. You must have Creator, Admin, or Owner privileges to share an agent.
Common Scenarios
Scenario: Department-specific agent in Slack
Keep visibility set to Private
Share with the specific department Group as Viewers
Share with 1-2 team leads as Editors to maintain the agent
Connect to Slack—only department members can access it in Slack channels
Scenario: Company-wide knowledge base for maximum reach
Set visibility to Public so everyone can access it
Connect to Slack or Microsoft Teams
Grant a small team of knowledge managers Editor permissions
All employees can use it in chat apps without needing an elvex account—perfect for scaling adoption
Scenario: Agent in development
Keep visibility set to Private while building
Share with a few colleagues as Editors for feedback
Do not connect to chat apps until ready
Switch to Public or share with specific groups once ready for broader use
Scenario: Executive team assistant
Keep visibility set to Private
Share only with the executive team Group as Viewers
Share with executive assistants as Editors
Connect to Microsoft Teams—only executives can access it, ensuring confidentiality
Note: Sharing is not available for users with Member or Consumer roles. You must have Creator, Admin, or Owner privileges to share an agent.