> ## Documentation Index
> Fetch the complete documentation index at: https://braintrust.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack alert permissions in project settings

export const plans_0 = "Any"

export const deployments_0 = "Any"

export const data_plane_version_0 = undefined

export const use_case_0 = undefined

<Note>
  **Applies to:**

  * Plan - {plans_0}
  * Deployment - {deployments_0}
  * {data_plane_version_0}
  * {use_case_0}
</Note>

## Summary

[Slack alert configuration](/admin/automations/alerts) has two permission levels: organization-level `Manage settings` permission is required to establish the initial Slack connection, while `Project: update` permission determines whether users can configure Slack channels for project alerts. This allows team members to manage alerts for their projects without access to sensitive organization settings.

## Permission Levels

### Organization Level: Connecting Slack

Organization-level `Manage settings` permission enables users to establish the initial Slack workspace connection in Organization Settings → Integrations. This must be done before any project-level Slack alerts can be configured.

### Project Level: Configuring Alert Channels

`Project: update` permission determines whether users can select Slack channels and configure alerts within individual projects. Once the organization Slack connection exists, users with this permission can access the Slack channel dropdown in the alert configuration dialog.

## Configuration Steps

### Step 1: Connect Slack (Organization Admin)

A user with `Manage settings` permission connects the Slack workspace to the Braintrust organization through Organization Settings → Integrations → Enable Slack.

### Step 2: Grant Project Permissions

Assign `Project: update` permission to team members who need to configure alerts for specific projects.

### Step 3: Configure Alert Channels

Users with `Project: update` can now access the alert dialog and select Slack channels when creating or editing project alerts.

## Permission Benefits

This permission model allows team members to manage alerts for their projects without granting access to organization-wide settings like API configurations or billing information.