> For the complete documentation index, see [llms.txt](https://docs.unskript.com/unskript-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unskript.com/unskript-documentation/tooling/notifications.md).
# Notifications
Customize your notifications from unSkript
Notifications can be set from your SAAS dashboard. IN the top menu, select **More -> Settings.**
There are two tabs that can be selected from the left: Integrations and Notifications.
## Integrations
{% tabs %}
{% tab title="Slack" %}
The Slack Integration connects unSkript to your Slack instance. Click the Slack button to begin.
A Slack page will open, asking for permission to connect to your workspace.
Change the workspace in the upper right hand corner.
You'll also be asked to select a channel. For the best experience -select a channel and not a DM.
The channel where Messages will be sent.
Name you integration, and then you're all set.
{% endtab %}
{% tab title="Email" %}
Coming Soon!
{% endtab %}
{% endtabs %}
## Setting Notifications
There are 5 notification types. Simple select the notification, choose the Integration you wish you use, and press **Apply.**
---
# 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.unskript.com/unskript-documentation/tooling/notifications.md?ask=&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.
