Skip to content

docs: document channel-based agent authorization for Slack #2034

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
inkeep wants to merge 1 commit into from
Closed

docs: document channel-based agent authorization for Slack #2034

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions agents-docs/content/talk-to-your-agents/slack/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,18 @@ When a team member uses `@Inkeep` or `/inkeep`, the app resolves which agent to
Channel defaults take priority over the workspace default. If you remove a channel default, that channel falls back to the workspace default agent.
</Tip>

## Automatic authorization

When you configure a workspace or channel default agent, users in those channels are automatically authorized to use that agent. This eliminates the need for admins to manually add each user as an explicit project member.

- **Channel defaults** — Users in the channel can execute the assigned agent
- **Workspace defaults** — All linked Slack users in the workspace can execute the assigned agent
- **Project-scoped** — Authorization is limited to the specific project the agent belongs to

<Note>
Users must still link their Slack account with `/inkeep link` before they can interact with agents.
</Note>

## Managing linked users

The dashboard shows all users who have linked their Slack accounts to Inkeep. You can:
Expand Down
Loading