---
title: Connect Slack to Illizeo
description: "The Slack connector is installed once for the whole company, by an administrator. Illizeo then writes into Slack as an app — never impersonating anyone. - **Read**5 min - **Level**Intermediate - **Updated**September 2026 - **Module**Integrations & API ## A company…"
url: "https://illizeo.com/en/centre-aide/connect-slack-to-illizeo/"
updated: "2026-10-16"
category: "Platform / Integrations & API"
---

# Connect Slack to Illizeo

The Slack connector is installed once for the whole company, by an administrator. Illizeo then writes into Slack as an app — never impersonating anyone.

- **Read**5 min
- **Level**Intermediate
- **Updated**September 2026
- **Module**Integrations & API

## A company connector, not a personal setting

Unlike the calendar and video connectors (Microsoft 365, Google, Zoom), which each employee plugs in for themselves, Slack is a **company** connector: one workspace per company, one bot token that writes into the customer’s Slack. Installing and disconnecting it require the *Apps and connectors* admin permission.

## Step by step

1. ### Start the installation

   From the connectors screen, pick Slack then *Connect*. You are redirected to your Slack workspace’s consent screen.
2. ### Read what is asked — and what is not

   Illizeo asks for a **bot** token and **no permission to act on your behalf**. The user-scope field is sent empty rather than omitted, precisely so the consent screen is explicit about what is not being requested.
3. ### Grant the five permissions

   The connector needs exactly five scopes, and nothing else.
4. ### Test the connection

   The *Test connection* button does not return a bare red light: if a scope is missing, it **names** it and states what it is for. A valid token missing a scope is not a connection failure — and the only remedy is a **reinstall**, not a token rotation.
5. ### Read the connector card

   Once connected, the screen shows your Slack workspace name, how many employees are matched and how many are not. The token itself is never displayed.

## The five permissions requested

| Slack scope | What it is for |
| --- | --- |
| `chat:write` | Post messages |
| `chat:write.public` | Post to a public channel without adding the bot to it |
| `im:write` | Open a direct message with an employee |
| `users:read` | List the workspace members |
| `users:read.email` | Match an Illizeo employee to their Slack account |

## What does not exist

No per-employee installation: one Slack workspace per company. Illizeo creates no Slack account, invites nobody, deactivates nobody and never modifies your Slack directory. No permission to act on behalf of the person installing is requested, so no message can ever be posted under their identity.

## FAQ

   Is there one Slack app per customer?

No. A single Slack app serves every customer workspace. Your company is identified by your workspace id, carried in Slack’s signed request — never by anything else.

   What happens if the token is revoked?

Sending falls back to email and administrators get an alert. One per hour only: a revoked token affects every subsequent send, and without that lock each HR notification would turn into an alert email.

   Can we disconnect?

Yes, from the same screen. Note that disconnecting on the Illizeo side does not remove the app from your Slack workspace — that is done in Slack.

   Why is a missing scope not a connection error?

Because the token is valid: it simply does not carry that permission. Slack only grants what the app asked for at install time, so a workspace installed before a scope was added keeps the old set until it is reinstalled.

### Match your employees

Once connected, Illizeo still needs to know which Slack account belongs to which employee.

[See all Platform articles](/en/centre-aide/?cat=platform)

### *Related*