> For the complete documentation index, see [llms.txt](https://docs.kyso.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyso.io/collaboration/business-notifications/slack.md). # Slack {% hint style="danger" %} Current limitation: all event notifications are sent to Slack and Teams from Kyso. There is no option (currently) to customise your own communications preferences. This is only possible for email communications. {% endhint %} Kyso can be integrated easily with Slack, which will receive notifications when something happens in your organization or channel, for example, when a new report is created, or a new comment is written, just follow these steps: ## 1. Create a Slack App Open Slack and choose the option **Apps**, under the menu *More.*

Click on **App Directory** button, located at the top right of your screen.

Then, click on **Build**, located at the top right of your screen.

Go to **Your Apps** in the top right of your screen, go to **Manage your apps** and click **Create an app**

Click **Create an app**

Select the option **From scratch**

Choose a **name** and select the desired **workspace**

Click on the section **Permissions.**

Scroll down until the section **Scopes** and add the scope **chat:write** to the **Bot Token Scopes.**

Scroll up to the top of the same page and click on the button **Install to Workspace.**

Copy the generated **Bot User OAuth Token** and save it for later use.

The Slack App configuration is finished, in the next section you will configure Kyso to use this Slack App. ## Configure Kyso Slack notifications can be configured at different levels: * **Organization level**. All the channels under an organization will *inherit* this configuration. That means, all the notifications related to that organization will use the same Slack channel. *Requires organization admin role*. * **Channel level**. Every channel can define their own slack notifications. If there is a configuration at organization level, that configuration will be *overwritten* by the channel configuration. Using this, you can define specific configuration per channel. Requires Full Access role. #### Configure Slack Notifications at Organization Level Login into Kyso, click on your avatar and select **Settings**.

Choose the desired organization in the left menu, select the tab **Notifications** and copy & paste the **Bot User OAuth Token** in the form *Slack Token*. Also, specify the **destination channel** in the input *Slack Channel*.

Open Slack, click on the **destination channel** and open the configuration by clicking on the title of the channel, at the top of the page.

Select the tab **Integrations** and click on the button **Add an App**.

Write the name of your app and click on the button **Add**.

Well done! Your organization is now configured with Slack, to test it out just create a new report in your organization and check that you are receiving the notifications in the configured channel at Slack.

## Configure Slack Notifications at the Channel Level The configuration process is exactly the same, but in the **Channel Configuration** page on your Kyso settings.

Take into account that the **slack token** only can be defined at the **Organization level**, for security reasons. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kyso.io/collaboration/business-notifications/slack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.