> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accessowl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

# Capabilities

<CardGroup cols={2}>
  <Card title="User Sync" icon="arrows-rotate">
    AccessOwl periodically syncs a list of users along with their assigned permissions.
  </Card>

  <Card title="Provisioning" icon="user-plus">
    AccessOwl creates or removes user accounts with the specified permissions during access requests or revocations.
  </Card>

  <Card title="Directory Sync" icon="folder-open">
    AccessOwl syncs (creates, removes, or deactivates) users from directories like Slack, Microsoft365, Okta, or Google into the AccessOwl users database.
  </Card>
</CardGroup>

# Setup

1. For automated provisioning either add a new application or open "Applications" and click the +-symbol and click continue

2. Follow the setup instructions and assign the integration account as a "Workspace Owner"

# User Groups

AccessOwl provisions Slack access through Slack User Groups. Each User Group carries its own set of channels, so assigning a User Group to a member grants them access to those channels.

We recommend creating team-based User Groups (for example @Marketing, @HR, @Engineering) mapped to the channels each team needs, then referencing them in your [Access Templates](/guides/onboarding-offboarding/access-templates). Onboarding then grants each new hire the right channels automatically.

<Note>
  User Groups are created and edited in Slack, not in AccessOwl. See Slack's [Create and edit user groups](https://slack.com/help/articles/212906697-Create-a-user-group) guide.
</Note>

# Troubleshooting

<AccordionGroup>
  <Accordion title="'Guest' or 'Multi-Channel Guest' requests are automatically reassigned">
    Currently Guest and Multi-Channel accounts can't be provisioned through AccessOwl. These need to be manually invited by stating the channels you want to grant access to.
  </Accordion>

  <Accordion title="Access revocation to remove a 'Workspace Admin' are automatically reassigned">
    AccessOwl can only remove Admins when the Integration Account's permission is "Workspace Owner"
  </Accordion>
</AccordionGroup>