Access List
Access List
Manage which users can run analyses against a project from chat triggers
The access list controls who in your organization is allowed to run analyses against a project from a chat trigger (Slack, Teams, Discord, Google Chat). When the list is empty, the project is open to every tenant member who can reach it from chat. As soon as you add a single user, the list becomes restrictive and only listed users can trigger analyses.
For the conceptual walkthrough — when to use it, who counts as "listed", and how it interacts with chat identity mapping — see Access list.
Endpoints
| Method + path | Purpose |
|---|---|
GET /v1/config/access-list | List allowed users for the project |
POST /v1/config/access-list | Add a user to the list |
DELETE /v1/config/access-list/{userId} | Remove a user from the list |
Project context
The access list is per-project. Every request to these endpoints must identify the project:
- A project-scoped API key implies the project automatically.
- A tenant-scoped key must send
X-Project-Idon every request.
See Authentication → Project scoping for details.
See also
- Access list guide — concepts and dashboard walkthrough
- Authentication — required permissions per endpoint
- Errors — error code reference