Channels
Notification channels and the project access list, both managed from the same page
The Channels page combines two related pieces of project configuration: notification destinations (channels) and a project-scoped allowlist for chat triggers (access list).
Channels section
A list of notification destinations for this project. Columns:
| Column | Notes |
|---|---|
| Type | Slack, Teams, Discord, Google Chat, Webhook, Email |
| Name | Your descriptive label |
| Threshold | Lowest severity that triggers this channel |
| Status | Active / Inactive |
| Actions | Edit, Toggle active, Delete |
Click Add Channel to create a new one. Type-specific fields appear based on the platform you select. See Notification Channels for per-platform setup.
Access list section
Below the channels list, the access list controls who can trigger chat-based analyses on this project. By default it's empty — meaning any team member can trigger.
To restrict, pick users from the dropdown and click Add User. Only listed users will be allowed to trigger via Slack/Teams/Discord/Google Chat slash commands.
See Access control for the full explanation, including identity mapping and channel bindings.
Required role
| Action | Required permission |
|---|---|
| View channels and access list | config:read |
| Add / edit / delete channels | config:write |
| Manage access list | config:write |
Quotas
Notification channels per project:
| Plan | Channels |
|---|---|
| Starter | 2 |
| Pro | 10 |
| Business | Unlimited |
| Enterprise | Unlimited |
The access list is uncapped — add as many users as you want.