Skip to main content

How permissions work with elvex assistants in Slack

Learn how permissioning works when connecting assistants to Slack

Updated yesterday

elvex assistants can be connected to sensitive datasources containing confidential company information. When these assistants are used in Slack, there's a risk of accidentally exposing this information in public channels or to unauthorized users. The permission system is designed to prevent this risk while allowing appropriate access.
​
This document will help you to understand how to control access to your assistant through Slack.


Permission Philosophy

elvex follows a security-first approach with Slack integration.

  • Default to safety: All assistants are disabled for Slack by default

  • Granular control: Permissions are set individually for each assistant

  • Workspace boundaries: Special considerations for shared channels and external workspaces

  • Identity verification: User matching between elvex and Slack accounts when needed

Assistant Slack permission settings

Slack permissions for elvex assistants are controlled individually for each assistant. To adjust permissions for an assistant, navigate to the assistant settings, then Slack Settings.

Once expanded, you'll see three possible permissions for your assistant:

  • All Slack users - Any member of your Slack workspace can use this assistant. When enabled, this assistant will be usable within public channels. This setting is only available for assistants with Public visibility.

  • Match elvex permissions - Slack access will be restricted to elvex users who have permission to use this assistant. Only members of your Slack workspace with an elvex account can use this assistant.

  • Disabled (Default) - The assistant will not be usable from within your Slack workspace. This is the default setting for all new assistants.

Permission Models Explained

All Slack Users

This permission model democratizes access to an assistant across your entire Slack workspace. It's appropriate for:

  • General-purpose assistants without sensitive data connections

  • Company-wide tools that everyone should be able to access

  • Assistants that provide public information or services

Private Assistants cannot use the "All Slack users" setting as this could potentially allow unauthorized users to access the assistant and its connected datasources.

Match elvex Permissions

This model creates a direct link between elvex user permissions and Slack access. It's ideal for:

  • Assistants connected to sensitive datasources

  • Tools that should only be accessible to specific teams

  • Maintaining consistent access control across platforms

With this setting, elvex verifies the Slack user's email address against elvex user accounts. Users can only access the assistant in Slack if they have permission to use it in elvex.

Assistants with this setting can be used in a channel (private or public) or via a Direct Message with the elvex app within Slack.

Disabled

The most restrictive option prevents any Slack access. This is appropriate for:

  • Highly sensitive assistants that should never be used in chat environments

  • Assistants still in development or testing

  • Internal tools that should only be accessed through the elvex platform

This is the default setting for new assistants.

Understanding Shared Channels and Slack Connect

Slack offers two ways to collaborate with external organizations:

  1. Shared Channels - Connect two workspaces together

  2. Slack Connect - Connect up to 250 organizations in a single channel

Both features create important security considerations for your elvex assistants:

  • External users may be present in these channels

  • Direct messages could be initiated by users outside your organization

  • Information shared in these channels could leave your organization's boundaries

  • Multiple external organizations might have access to the same channel (especially with Slack Connect)

The elvex permission system works consistently across both Shared Channels and Slack Connect. The "Allow Shared Channels" setting should be enabled only when you're confident that the assistant is appropriate for potential external visibility, regardless of whether you're using traditional Shared Channels or Slack Connect.

When enabled, the same permission model you've selected ("All Slack Users" or "Match elvex Permissions") will apply to both Shared Channels and Slack Connect interactions.


Still having issues? Check the FAQ

Did this answer your question?