Skip to main content
Slack provides AI agent tools for managing user membership across an Enterprise Grid org. Reference these tools in using @ mentions to automate workspace assignment, guest expirations, and offboarding during ticket handling.
The Enterprise Admin tools below only work on Slack Enterprise Grid installs that have an admin token connected. A Slack org admin must complete the connection from Settings → Integrations → Slack → Connect Enterprise Admin before these tools can run.

​
Available tools

Assign user to Enterprise workspace

Adds a user who already exists in your Enterprise Grid org to a specific workspace. No invite email is sent — the user is added directly with the role you specify.Tool name: @Assign User to Slack Enterprise WorkspaceInput fields:
  • Workspace — teamId (T…) or teamName (e.g., engineering). The tool resolves the name to an ID automatically.
  • User — userId (U…) or email. The tool resolves the email to a Slack user ID automatically.
  • Role — one of:
    • regular — full member
    • multi_channel_guest — access to specific channels
    • single_channel_guest — access to exactly one channel
Common use cases:
  • Add new hires to the right workspaces as part of onboarding
  • Grant a contractor guest access to a project workspace
  • Move a user into an additional workspace when their team changes
Example rule:

Assign new hire to workspace

Sets or updates the access expiration timestamp for a guest user in an Enterprise Grid workspace. Use this to enforce time-bound access for contractors and vendors.Tool name: @Set Enterprise User Access ExpirationInput fields:
  • Workspace — teamId (T…) or teamName.
  • User — userId (U…) or email.
  • expirationTs — Unix timestamp in seconds when guest access should expire.
Common use cases:
  • Set an end date when granting contractor or vendor access
  • Extend an existing guest’s access when their engagement is renewed
  • Shorten access when a project wraps up early
Example rule:

Set guest expiration for contractor

Removes a user from a single workspace inside the Enterprise Grid org. The user keeps their Slack account and access to any other workspaces they belong to.Tool name: @Remove User from Slack Enterprise WorkspaceInput fields:
  • Workspace — teamId (T…) or teamName.
  • User — userId (U…) or email.
Common use cases:
  • Remove a user from a workspace when they change teams
  • Clean up guest access after a project ends
  • Revoke workspace membership as part of partial offboarding
Example rule:

Remove contractor from workspace

​
Setup

1

Install the Slack integration

Follow the Slack setup guide to connect Slack to Ravenna.
2

Connect the Enterprise admin token

A Slack org admin must connect the Enterprise admin token from Settings → Integrations → Slack → Connect Enterprise Admin. Without this token, the Enterprise admin tools return an ENTERPRISE_ADMIN_TOKEN_REQUIRED error.
3

Configure your agent

Open your agent’s settings and confirm the Slack tool appears in the Tools section under Capabilities.
4

Create rules

Write that reference the Slack tools using @ mentions.
5

Test the tools

Test rules against a non-production workspace first to confirm the agent assigns the role, expiration, or removal you expect.

​
Best practices

  • Always confirm the workspace and role with the requester before running Assign User. The role choice (regular, multi_channel_guest, single_channel_guest) is not reversible without removing and re-adding the user.
  • Prefer email over userId and teamName over teamId in rule prompts — both are easier for end users to provide on tickets, and the tools resolve them automatically.
  • Pair Set Enterprise User Access Expiration with your contractor onboarding workflow so every guest is created with an end date.
  • Use Remove User from Enterprise Workspace for partial offboarding only. To fully deactivate a Slack user, use your identity provider (for example, Okta or Microsoft Entra) instead.
Learn more about configuring agents and writing effective rules
Last modified on June 22, 2026