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

# Slack

> Connect Slack to ask Vidoc questions in channel threads and to get a daily security digest.

<Note>
  **Vidoc Cloud only.** Self-hosted installations do not have the Slack integration.
</Note>

With the Slack integration, your team can:

* Mention Vidoc in a Slack channel and ask about code and findings.
* Get a daily security digest in a channel.

You need the Admin role to set up the integration.

## Connect a Slack workspace

1. Open **User menu > Slack Integration**, or open **Integrations** and click the Slack card.
2. Click **Connect Slack**.
3. In Slack, select the workspace and allow the Vidoc app.
4. Vidoc opens again and shows **Slack workspace ... connected**.

One Vidoc organization connects to one Slack workspace. If the workspace is connected to a different organization, disconnect it there first.

## Set the default project

Vidoc uses one project for all mentions in the workspace. Vidoc selects the project that was open when you connected Slack.

To change it:

1. In **Default project for Slack mentions**, select the project.
2. Click **Save default project**.

A Vidoc admin can also change it in Slack with `/vidoc-set-project <project-name>`. Vidoc matches the Slack user to a Vidoc user by email. The command works only for Vidoc admins.

## Ask Vidoc in Slack

1. Add the Vidoc app to the channel.
2. Mention Vidoc in a message, then type your question.
3. Vidoc replies in the thread of your message. It reads the earlier messages of the thread. To ask a follow-up question, mention Vidoc again in the same thread.

Vidoc can:

* Answer questions about the repositories, findings, and pull requests of the default project.
* Read the code of a repository in the project to answer a question.
* Tell you which findings to fix first.
* Change the status or the severity of a finding when you ask for it. To ignore a finding, give a reason.
* Remember a fact about your code or your policy when you ask for it. Refer to [Memory from Slack](#memory-from-slack).

Vidoc uses the project [Memory](/web-app/memory) when it answers.

<Warning>
  For project questions and finding changes, Vidoc does not check each Slack user's Vidoc role or project membership. Channel members can ask for code and findings from any repository in the default project, change finding status or severity, and save project or repository memory. Add the app only to channels whose members are authorized for all of that access. Use a separate Vidoc project when repositories have different audiences.

  Organization-wide memory is an exception: Vidoc verifies that the Slack user's email matches a Vidoc admin in the connected organization before saving it.
</Warning>

## Memory from Slack

When you ask Vidoc to remember a fact, for example "Remember that all admin endpoints are behind the VPN", Vidoc saves it for the project or a repository, depending on your request. A verified Vidoc admin can also request organization-wide memory. State the intended scope in your request. The validation agent uses applicable entries in later validations, the same as memory entries from PRs.

The entry shows on the [Memory](/web-app/memory) page with the source **Slack**. There is no approval step. Examine Slack entries regularly and supersede the wrong ones. Refer to [Review Memory regularly](/web-app/memory#review-memory-regularly).

## Daily security digest

Vidoc posts a short security digest to a Slack channel every weekday (Monday to Friday). The digest shows the one most important issue to fix now, with its location, the action, and the reason. If your team fixed issues recently, the digest also shows this progress. If nothing needs action, the digest says so.

The organization has one digest schedule. To set it:

1. In **Scheduled security digest**, set these fields:

   | Field                                 | Value                                                                                                                                             |
   | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Project**                           | The project for the digest.                                                                                                                       |
   | **Channel**                           | A public channel name, for example `#security-alerts`. For a private channel, paste the channel ID and invite the Vidoc app to the channel first. |
   | **Hour (0–23)** and **Minute (0–59)** | The time to post.                                                                                                                                 |
   | **Timezone (IANA)**                   | For example `Europe/Warsaw`. By default, the time zone of your browser.                                                                           |
   | **Enabled**                           | Clear it to pause the digest and keep the settings.                                                                                               |

2. Click **Create schedule**, or **Save changes** for an existing schedule.

3. Click **Send test message**. Vidoc posts a test message to the channel. If Slack rejects the message, Vidoc shows the error.

If a digest fails, the section shows the time and the error of the last failure.

## Disconnect Slack

Click **Disconnect Slack**. Vidoc stops replying to mentions. To remove the app from Slack fully, a Slack admin also removes it in the Slack workspace settings.