> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/other-integrations/slack.md).

# Slack

Request recordings, share videos, start calls and get new recording notifications without leaving Slack.

The Slack integration brings Screendesk into the Slack conversations where your team already helps customers. From any message, you can ask for a screen recording, record a video reply, start a video call, share a booking link or share a video from your library. Screendesk can also post new recordings to a Slack channel as they arrive.

{% hint style="info" %}
This page covers the **Slack integration** under **Settings → Integrations**. Folder automations that post to Slack when items land in a folder use a separate Slack connection. See [Slack Automation](/organization-and-workflows/automations/slack.md).
{% endhint %}

## How it works

Once an admin connects Slack, every agent in your workspace can use Screendesk from Slack:

* **Request a recording** — post a **Record your screen** button so a customer can show you the problem.
* **Record a video reply** — record your screen and paste the link into the conversation.
* **Start a call** — post a **Join call** invitation to a Screendesk video call.
* **Share a booking link** — post a **Choose a time** button so the customer can book a call.
* **Search and share a video** — find a video in your library and post it.

When a customer sends a recording you requested, Screendesk replies in the same thread with a **Recording received** card. You can also send every new recording to one notification channel.

Actions are always started by an agent. Screendesk never scans your conversations.

## Availability

The Slack integration is available on **all plans**. **Start a call** and **Share a booking link** need video calls on your plan.

## Connecting Slack

Only **workspace admins** can connect Slack. If you are not an admin, the **Connect** button is disabled.

{% stepper %}
{% step %}

### Open the Integrations page

Go to **Settings → Integrations** in Screendesk and find the **Slack** card.

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FEg3zcMZuQ9WK69GMFA5v%2FCleanShot%202026-02-09%20at%2015.30.49%402x.png?alt=media&amp;token=df30ebd5-2c4d-483b-8e6d-c603ec1fd2a4" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Start the connection

Click **Connect**. Slack opens and asks you to approve the Screendesk app.
{% endstep %}

{% step %}

### Choose a notification channel

Pick the Slack workspace and the channel where new recording notifications should go. Click **Allow**.
{% endstep %}

{% step %}

### Confirm the connection

You are taken to the Slack settings page in Screendesk. The Slack card on the Integrations page now shows **Connected** and the name of your Slack workspace.
{% endstep %}
{% endstepper %}

Agents can start using Screendesk from Slack right away. Each agent links their own account the first time. See [Linking your Slack account](/other-integrations/slack.md#linking-your-slack-account).

{% hint style="info" %}
One Screendesk workspace connects to one Slack workspace. A Slack workspace can be connected to only one Screendesk workspace at a time. If it's already connected elsewhere, an admin of that Screendesk workspace must disconnect it first.
{% endhint %}

### Already connected Slack before? Reconnect once

If your workspace connected Slack before the new actions were available, an admin needs to reconnect once. This adds the actions and the permissions they need, such as link previews.

1. Go to **Settings → Integrations** and find the **Slack** card.
2. Click **Reconnect** and approve the app in Slack.

Your notification channel and settings are kept. If the Slack card shows **Not connected**, click **Connect** instead.

## The Slack settings page

Click **Configure** on the Slack card to open the Slack settings page. Only admins can open it. Other members see a short summary on the Slack card.

### Recording notifications

* **Pause** or **Resume** notifications. While notifications are paused, Slack actions and replies in threads keep working.
* **Change channel** opens Slack's channel picker so you can choose a different notification channel.

### Slack actions

Turn each action on or off. Each switch covers both the message shortcut and the matching `/sd` command.

**Start a call** and **Share a booking link** can only be turned on if video calls are on your plan.

Slack still lists every Screendesk shortcut. If an agent picks an action that's turned off, Screendesk shows them a private note saying an admin turned it off.

### Linked agents

See which members have linked their Slack account. Click **Unlink** to remove someone. Their Slack actions stop until they link again, which Screendesk asks them to do the next time they use an action.

### Connection

* **Reconnect** keeps your linked agents, your notification channel and your notification setting.
* **Disconnect Slack** stops all actions and notifications. The history of past requests is kept.

## Linking your Slack account

The first time you use a Screendesk action in Slack, a dialog asks you to link your Screendesk account. You only do this once.

{% stepper %}
{% step %}

### Select Link my account

In the Slack dialog, select **Link my account**. Screendesk opens in your browser.
{% endstep %}

{% step %}

### Sign in and link

Make sure you are signed in to the right Screendesk workspace. Check the email and workspace shown, then click **Link account and continue**.
{% endstep %}

{% step %}

### Go back to Slack

Return to the Slack dialog and select **Continue**. Your action picks up where you left off.
{% endstep %}
{% endstepper %}

To link, you need an active membership that can create recordings. Watch-only members can't use Slack actions.

Linking your account:

* Doesn't add a seat or change your billing.
* Uses the role and access you already have in Screendesk.
* Keeps a link to the Slack message or thread you acted on. Screendesk never reads channel history or stores message text.

## Using Screendesk from Slack

There are two ways to start an action:

* **From a message:** hover over the message, open **More actions**, and choose a Screendesk action under **Connect to apps**. If you don't see it, select **More message shortcuts**. The result is posted as a reply in that message's thread.
* **With the `/sd` command:** type a command in the channel's message box. The result is posted as a new message in the channel.

Type `/sd` or `/sd help` to see the list of commands. Only you can see the list.

{% hint style="info" %}
Slack doesn't run slash commands inside threads. To act inside a thread, use the message's **More actions** menu instead.
{% endhint %}

| Action                   | Command        | What gets posted                           |
| ------------------------ | -------------- | ------------------------------------------ |
| Request a recording      | `/sd request`  | A **Record your screen** button            |
| Record a video reply     | `/sd reply`    | Nothing. You paste the link yourself       |
| Start a call             | `/sd call`     | A **Join call** button                     |
| Share a booking link     | `/sd schedule` | A **Choose a time** button                 |
| Search and share a video | `/sd search`   | A video card with a **Watch video** button |

### Request a recording

Use this when you need the customer to show you what's happening.

Screendesk posts "**\[Your name]** requested a screen recording" with a **Record your screen** button. The customer clicks it and records in their browser.

* From a message's menu, the request is posted in that thread.
* With `/sd request`, it's posted in the channel.

When the recording has finished processing, Screendesk replies in the same thread with a **Recording received** card. This can take a few minutes after the customer finishes recording.

Recording links don't expire. A link stops working only if your access is removed, your Slack account is unlinked, or Slack is disconnected.

#### From Slack's / menu

**Request a recording…** also appears when you type `/` in Slack's message box. Screendesk asks which channel to post in and pre-selects the conversation you're viewing. This always posts a new message. To answer inside a thread, use the message's menu instead.

### Record a video reply

Use this to answer with a video of your own screen.

1. Choose **Record a video reply** from the message's menu, or type `/sd reply`.
2. In the dialog, select **Open recorder**. The recorder opens in your browser.
3. Record and save your video.
4. Copy the shareable link the recorder shows. Choose **With DevTools** or **Content only**.
5. Paste the link into the Slack conversation.

Saving the video doesn't post anything to Slack. Your reply is only shared when you paste the link.

### Start a call

Screendesk posts "**\[Your name]** invited you to a video call" with a **Join call** button. The customer joins as a guest. You host the call in Screendesk.

If the call can't be created, Screendesk tries again. If it still fails, you get a private message in Slack and nothing is posted to the channel.

### Share a booking link

In the message menu this action is called **Schedule a call**.

Choose one of your active instant booking links. Screendesk posts "**\[Your name]** shared a booking link" with a **Choose a time** button. The customer picks a time on your booking page. Nothing is booked from Slack.

### Search and share a video

Search your library by title. AI-generated titles are included. Only videos you can access and that allow anyone with the link are listed.

Screendesk posts a card for the video with a **Watch video** button.

## Recording cards

Screendesk posts a recording card in two places:

* **Recording received** — in the original thread, when a recording you requested has finished processing.
* **Recording notifications** — in your notification channel, when a new recording arrives in your workspace. The card says who sent it and where it came from.

Each card shows:

* The recording's title (AI-generated when available), linked to the recording
* A short AI summary
* The duration and a small thumbnail
* A **View in Screendesk** button

Slack opens images in its own viewer, so click the title or **View in Screendesk** to open the recording.

### Send to Jira, Linear or GitHub

Cards can also show **Send to Jira**, **Send to Linear** or **Send to GitHub** buttons. The button opens the recording in Screendesk with the issue form ready to fill in. Your usual permissions and the review step still apply.

* On **Recording received** cards, the buttons match the tools the requesting agent connected.
* On notification cards, the buttons match the tools any member of your workspace connected.

Members connect these tools under **Profile → Integrations**.

### Recordings with restricted sharing

If a recording isn't shared with "anyone with the link", Slack shows no title, thumbnail or summary. The card only explains that details are hidden and shows the **View in Screendesk** button. Opening the recording still follows its sharing settings.

{% hint style="info" %}
Pausing recording notifications only affects the notification channel. **Recording received** replies in threads and all Slack actions keep working.
{% endhint %}

## Link previews

When someone pastes a link to a Screendesk recording from your workspace into Slack, Slack shows a preview. Most previews can play the video in Slack. They show the AI summary and a **View in Screendesk** button.

Previews work for recording links and short Screendesk links. Only recordings that anyone with the link can watch get a preview. A preview never changes who can see a recording.

{% hint style="info" %}
Link previews need the latest connection. If your workspace connected Slack before previews were available, an admin should [reconnect once](/other-integrations/slack.md#already-connected-slack-before-reconnect-once).
{% endhint %}

## Channels

* **Public channels:** Screendesk joins automatically when it needs to post.
* **Private channels:** a channel member must invite Screendesk first. Type `/invite @Screendesk` in the channel.
* **Archived channels:** Screendesk can't post in them.

If Screendesk can't post, you get a private Slack message explaining why. Nothing is posted to the channel.

## Permissions required

Screendesk asks for these Slack permissions when you connect or reconnect:

| Permission               | Why it's needed                                        |
| ------------------------ | ------------------------------------------------------ |
| **Slash commands**       | Run the `/sd` command                                  |
| **Send messages**        | Post requests, invitations, videos and recording cards |
| **Join public channels** | Post in public channels without a manual invite        |
| **Incoming webhook**     | Let you choose the notification channel in Slack       |
| **Read and show links**  | Show previews of pasted Screendesk links               |

## Privacy

* Every action is started by an agent. Screendesk doesn't scan your conversations.
* Screendesk doesn't read channel history.
* Screendesk stores a reference to the channel and thread you acted on. It doesn't store message text.
* Cards and previews never widen who can see a recording.

## Good to know

* **Admin-only setup.** Only workspace admins can connect, configure, reconnect or disconnect Slack.
* **One notification channel.** All recording notifications go to one channel. Use **Change channel** on the Slack settings page to pick another.
* **Works alongside other notifications.** Slack doesn't change your email or in-app notification settings.
* **Need more control?** For channel-per-folder routing or custom messages, use [Folder Automations](/organization-and-workflows/automations.md) with a Slack automation.

{% hint style="warning" %}
If someone removes the Screendesk app from your Slack workspace (in Slack's app management), Screendesk disconnects automatically. An admin can connect again at any time.
{% endhint %}

## Troubleshooting

<details>

<summary>I don't see the new Screendesk actions in Slack</summary>

If your workspace connected Slack a while ago, an admin needs to reconnect once. Go to **Settings → Integrations**, find the Slack card, and click **Reconnect**. If the card shows **Not connected**, click **Connect**.

In the message menu, Slack shows only a few shortcuts at first. Select **More message shortcuts** to see all of them.

</details>

<details>

<summary>The /sd command doesn't work in a thread</summary>

Slack doesn't run slash commands inside threads. Open the message's **More actions** menu and choose a Screendesk action under **Connect to apps**.

</details>

<details>

<summary>Slack says an admin turned off this action</summary>

An admin turned the action off on the Slack settings page. Ask them to turn it on under **Settings → Integrations → Slack → Configure**.

</details>

<details>

<summary>I can't link my account</summary>

Check the following:

* You are signed in to Screendesk with the right email and workspace. If not, sign out and open the link from Slack again.
* Your membership is active and can create recordings. Watch-only members can't use Slack actions.
* The **Link my account** link expires after 30 minutes. Go back to Slack and start the action again to get a new one.
* Each member can link one Slack account per workspace. If your Slack account is linked to another member, or your member account is linked to another Slack account, ask an admin to unlink it.

If you select **Continue** before linking, Slack reminds you to link first. Nothing is sent.

</details>

<details>

<summary>Screendesk couldn't post in a channel</summary>

You get a private message from Screendesk explaining why. Usually:

* **Private channel:** a channel member needs to invite Screendesk with `/invite @Screendesk`.
* **Archived channel:** run the action again from an active channel.
* **Missing permission:** ask an admin to reconnect Slack.

</details>

<details>

<summary>There are no booking links to share</summary>

**Share a booking link** lists your active instant booking links. Set one up in Screendesk, then try again. If Slack says a booking link isn't ready, check its calendar connection in Screendesk.

</details>

<details>

<summary>A recording card or link preview shows no title or thumbnail</summary>

The recording isn't shared with "anyone with the link". Slack only shows details for recordings anyone with the link can watch. Click **View in Screendesk** to open it if you have access.

Link previews also need the latest connection. Ask an admin to reconnect Slack.

</details>

<details>

<summary>I'm not receiving recording notifications</summary>

Check the following:

* On the Slack settings page, notifications are not **Paused**.
* The notification channel still exists and isn't archived.
* Notifications are posted shortly after a recording finishes processing. Wait a few minutes after a test recording.

</details>

<details>

<summary>I can't connect a different Slack workspace</summary>

A Screendesk workspace stays tied to the Slack workspace it first connected, so its request history is kept. If you need to move to another Slack workspace, contact Screendesk support.

If Slack says the workspace is already connected to another Screendesk account, an admin of that account must disconnect Slack first.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/other-integrations/slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
