> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelset.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up Slack for your store
> Connect your Slack workspace, pick a default channel, link your team so they can ask Levi in Slack, test it, and create a first automation that posts to a channel
Connecting Slack does two separate things. Your team can ask Levi, the assistant built into Levelset, questions in Slack, and Levi answers each person with their own access. And **automations**, the rules that send a message when something happens in Levelset, can post in the channels you pick, where everyone in the channel reads the same message. Setup takes a few minutes.
Open **Organization > Set up > Integrations** and find the **Slack** card. Once Slack is connected, the card shows a **Set up Slack** checklist with the five steps below, in the same order. Each ticks by itself when it's done; click an open step to go to it.
Already connected and here to link people? Go to [Link your team](#link-your-team).
## Connect Slack
Say your store wants leaders to ask Levi about ratings from Slack, and a post in its leaders' channel whenever a discipline form is submitted.
1. On the **Slack** card, click **Connect Slack**. Slack opens in the same window.
2. In Slack, pick your store's workspace and approve Levi. You come back to the card, which reads **Connected** and shows the workspace's name.
Finish the Slack step within ten minutes, or start again from the card. Two things can stop the connection. On Slack's free plan a workspace can install only a limited number of apps; if the card says your workspace has reached its app limit, remove an app you no longer use in Slack and click **Connect Slack** again. And some workspaces only let a Slack admin approve new apps; if the card says Slack did not let Levi in, ask whoever manages your Slack workspace to approve Levi, then connect again.
One Slack workspace connects to one Levelset organization. If the workspace is already connected to another organization, the card says so.
## Pick a default channel
The **default channel** is where automations post unless they name another channel, and where the test message goes. In the example, that is the leaders' channel. Pick it under **Default channel** on the card. The list holds every public channel, and Levi adds itself to the one you pick. A private channel shows up only after someone adds Levi to it in Slack.
To check the connection, click **Send a test message**. Levi posts "Levi is connected." in the channel, and the card confirms it. If Slack refuses, the card says why; usually Levi was removed from the channel, so add it back in Slack or pick another channel. The test message shows that Levi can post; it doesn't tick the **Ask Levi something in Slack** step.
## Link your team
A **member link** ties a Slack account to a person in Levelset. Levi answers someone in Slack only when their account is linked, because the link is how Levi knows whose access to answer with. Linking happens in the member review, a window listing your Slack members. It opens by itself right after the first connection; later, open it with **Review member links**.
The review sorts your Slack members. Under **Suggested**, members whose Slack email matches someone in Levelset are already picked, and **Link all 12 email matches** (with your own count) links every one of them in one click. A phone or name match is offered first in that member's menu but isn't picked for you, so check it before choosing it. For anyone else, pick the right person or leave **Don't link**, then click the button that links them, for example **Link 3 members**.
When you pick a person, the review shows whether they can use Levi in Slack. **No Levelset login** means Levi can't answer them until they're invited to Levelset; see [Access](/team/access). **Can't ask Levi** means they have a login, but their role doesn't include the permission to ask Levi at their own store, or your organization's plan doesn't include Levi. The checklist step then reads, for example, "12 of 20 Slack members linked. 9 can use Levi."
Someone who messages Levi before they're linked is asked to pick their own name from a list, but that pick is only a claim: it links nothing until it's confirmed in the review, where it shows as **Claimed by the member**. The person who reviews member links gets a notification from Levelset about each new claim, and the card shows how many are **waiting for review**. The reviewer is whoever connected Slack; if their login is no longer active, or they can no longer edit forms, anyone who can edit forms can review.
## Ask Levi something in Slack
Try Levi yourself: send it a direct message (open **Levi** under **Apps** in Slack), or type @Levi in a channel Levi is in, such as your default channel, followed by a question like "How did ratings go this week?". The **Ask Levi something in Slack** step ticks once Levi has answered anyone in this workspace.
Then tell your team. The **Share with your team** box on the card holds a short message explaining how to reach Levi and what it can answer, in English or Spanish. Click **Copy** and paste it in Slack. What your team can ask, and how Levi answers in a channel compared with a direct message, is on [Ask Levi in Slack](/levi/slack).
## Create an automation that posts to Slack
Click **Create an automation that posts here** on the card, or the last checklist step, to open **Workflows > Automations**. Building the rule is covered in [Create an automation](/forms/automations#create-an-automation); for the example, the rule fires when a discipline form is submitted. Under **Deliver via**, tick **Slack** and pick the channels. The step ticks once any automation posts to this workspace.
Everyone in a Slack channel sees what an automation posts there, including people whose Levelset access wouldn't show them that information.
While you build the rule, Levelset checks the channel's members and warns you under the channel picker when some of them can't see what the message carries: discipline details, ratings, evaluation results or a form's answers. The warning names how many members that is, for example "12 of 15 members can't see that in Levelset". Members who aren't linked, or have no login, count as unable to see it. The same warning shows again after you save.
The warning never blocks the save and never changes the message: the rule still posts exactly what you wrote. Who is in the channel is your team's decision. If the warning matters, post to a channel limited to the right people, or take those details out of the message. Position averages don't raise a warning, since everyone can see them. If Slack doesn't answer, the warning says the channel couldn't be checked, which doesn't mean it's fine.
## Who can do what
| If you notice this | The permission behind it |
| - | - |
| **Integrations** is missing from the **Organization** menu | Forms > Edit Forms |
| **Can't ask Levi** next to someone with a login | Levi > Use Levi, at that person's store |
| The review says only the person who connected Slack can review member links | Not a permission of yours: that person is still active and can edit forms, so the review is theirs |
If you're missing something here, ask whoever manages roles in your organization to turn it on. See [Roles](/team/roles).
## Common questions
Levi tells them why in Slack. The usual reasons are no Levelset login yet, a role without the permission to ask Levi, or a login that was removed or made inactive. Whoever manages logins in your organization fixes that on the **Access** tab of **People > Team & Access**; then have them ask again.
Only an email match is picked for you. A member whose Slack email doesn't match anyone in Levelset is listed under **Needs a choice** or **Not in Levelset** instead. Find them there and pick the right person from their menu.