Skip to main content
Private alpha. OpenWork in Slack must be enabled for your organization by a platform administrator. This guide is public; it does not grant alpha access. Contact the OpenWork team to request access. Slack’s agent features must also be available in your workspace.
Mention @openwork in a channel or DM it to work with your own OpenWork connections and permissions. Each member connects their own Slack account. Installing the bot once does not sign everyone in.

Who does what

Ask your agent to set it up

Give an agent with browser or computer access this prompt:
The agent can inspect the setup, merge the manifest, verify event delivery, configure replies and channel limits, and test the bot. A Slack administrator authorizes installation; every member authorizes their own account. Your agent’s tool permissions still apply.

How replies and permissions work

  • The person who mentions or DMs @openwork is the only actor. The assistant uses that member’s own Slack and connected-service access, not a shared account.
  • Two members in the same Slack thread get separate OpenWork sessions.
  • DMs and private rollout replies stay in the invoking member’s DM. Channel replies are visible to the channel when private replies are off.
  • If the assistant needs a permission decision, continue in OpenWork Web. Slack does not approve it for you.
This assistant builds on the Slack MCP connection. Set that up first if your organization does not have one yet.