> ## Documentation Index > Fetch the complete documentation index at: https://docs.reasonos.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect Slack > Turn a Slack message into a ReasonOS issue, link a message to an issue you already have, and let an issue's status reach the thread it came from. ReasonOS has one Slack app per cloud. An organization administrator installs it into the organization's Slack workspace once; after that, anyone in the workspace who has linked their Slack account to their ReasonOS account can create or link issues from a message, and a project can choose to show issue previews or send status updates back into Slack. Slack is available with the core ReasonOS product. This page is for the administrator who connects the workspace. For what members can do once it is connected, see [Use Slack with Work](/platform/slack-guide). A channel can also receive short issue notices without the app, through an incoming webhook: see [Slack issue notifications](/platform/slack-notifications). ## What the app does * **Create ReasonOS issue** (a message shortcut, in the message's **More actions** menu): opens a form filled from the message. You choose the project, edit the title and description, and confirm. The issue records where it came from; nothing is posted to the channel. * **Link to ReasonOS issue** (a second message shortcut): links the message to an issue you name by number. The issue's title and description are left as they are. * **`/reasonos`**: opens the same form with the command's text as the title, or filled from one of the project's issue templates with `/reasonos --template `. The channel needs a project default (below) for the template form. * **Status updates in the thread**: an organization administrator who can write the issue and has linked their own Slack account can switch on, from the issue page, a single thread that receives the issue's key, title, a link to it and a lifecycle word when its status changes. Nothing else about the issue is posted. * **Reply sync** and **issue previews** are opt-ins a project's administrator switches on separately; each needs an extra permission that the app asks for only when it is turned on (see below). * **Channel feeds**: a project administrator can post the project's issue activity into a channel of the project's choice, and an organization administrator can post an initiative's published updates — as it happens, or as a daily or weekly summary. These use the app's existing permissions and need no reconnect. (A channel can still receive the older [issue notices](/platform/slack-notifications) through an incoming webhook.) * **Personal notifications**: a member who has linked their account can choose to receive direct messages from the app about their own issues (assignments, mentions, status changes, a daily due-date digest). Off for everyone until the person switches it on, and only possible after an administrator has allowed direct messages (below). Issues are created, linked, previewed and updated in channels that belong to your workspace alone: public channels from the start, and private channels the app has been invited to once an administrator has chosen **Allow private channels** (below). Shared channels are refused, including Slack Connect, organization-wide sharing and sharing that is still pending, and so are archived channels and direct messages (the only direct messages are the personal notifications the app sends, below). Slack apps with token rotation turned on are not supported either. ## Connect a workspace Open **Settings → Integrations → Slack** and choose **Connect Slack**. Slack asks you to pick the workspace and to approve the permissions listed below; you land back on the page with the workspace shown. * Only organization administrators can connect, reconnect or disconnect. * **One Slack workspace per organization.** Connecting a second workspace is refused; disconnect the first one to change it. * If the page says *Slack isn't set up on this installation*, the ReasonOS deployment you use has no Slack app yet. Ask whoever operates it. Under **Channel defaults** an administrator can map a channel to a project, so the create form opens on that project. A default grants nobody any permission; the person creating the issue still needs write access to the project's Work. ## Link your Slack account Each person links their own account once. Run either shortcut on any message: instead of the form, a private **Link your account** dialog opens for you alone, with a **Link account** button. Press it, sign in to ReasonOS if you are not already, and confirm the account shown on the page is yours. Then run the shortcut again. * The link is for you alone, works once and expires after ten minutes. A link that has expired or was opened before sends you back to the Slack settings page with a note to start again from the shortcut. * Only a signed-in person can confirm; an access token or a branch server cannot link an account for you. * Your linked accounts are listed under **Your Slack account** on the Slack settings page, where you can unlink them. ## Which permissions are asked, and when The app asks Slack for the smallest set it needs, and asks for more only when an administrator turns on the feature that needs it. | When | Permission | Why | | - | - | - | | Connect Slack | `commands` | the shortcuts and the `/reasonos` command | | Connect Slack | `channels:read` | to check that a channel is public and not shared | | Connect Slack | `chat:write` | to post the status updates a thread opted into | | Reconnect to sync replies | `channels:history` | to receive new replies in a thread an administrator switched **Sync replies with Slack** on for; no earlier messages are read | | Reconnect to show previews | `links:read`, `links:write` | to show an issue's key, title and status when its link is posted in a channel the project opted in | | Reconnect to allow direct messages | `im:write` | to open a direct message with a member who switched their own notifications on; nobody receives anything until they do | | Allow private channels | `groups:read`, `groups:history` | to check that a private channel the app was invited to belongs to your workspace, and to receive replies there when reply sync is on. The grant alone does not import messages or start posts: shortcuts require an explicit action, and sync, previews and feeds still require their own opt-in | The **Reconnect** actions are on the Slack settings page next to the workspace, and each repeats Slack's approval screen with the added permission. A workspace connected before status updates existed also shows **Reconnect to allow posting**, which asks for `chat:write`; a workspace connected today has it from the start. Reconnecting keeps every permission the workspace already granted. Reconnecting never turns a feature on by itself: reply sync is enabled per issue from its page, previews per project and channel under **Project settings → Work → Slack previews**, channel feeds under **Project settings → Work → Slack feeds** and **Settings → Initiative feeds**, and direct messages by each member for themselves under **Slack notifications** on the Slack settings page. **Allow private channels** is the same kind of step: it lets private channels be chosen where public ones can, and a workspace that never takes it keeps working in public channels only. Settings rows that name a private channel say **private** beside it. The app never asks for a person's name, email or files, and it never reads a conversation nobody switched on: the history permission that reply sync asks for is used only for new replies in threads an administrator explicitly syncs. ## Disconnect On the Slack settings page choose **Disconnect** next to the workspace and confirm. Do it here, not only in Slack: removing the app from Slack's side stops it from posting and from answering shortcuts, but ReasonOS keeps the connection, the account links and any open forms until you disconnect here. * Every shortcut, command, reply, preview and status update for that workspace stops immediately. * Every member's account link and any form still open is invalidated; people link again after a reconnect. (Unlinking a single account, by contrast, affects only that person: their replies are no longer imported, and a thread they switched on stops posting until someone switches it on again.) * Issues already created stay in Work, with their comments and the record of the message they came from. A preview or an update already posted in Slack is not recalled. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.