> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/workspaces/workspace-notification-destinations.md).
# Configuring notification destinations for a workspace
When a workflow job completes, fails, or is canceled, or is canceled, Fabricate sends a notification to the enabled notification destinations.
Notification destinations include email addresses, Slack webhooks, and Microsoft Teams webhooks.
### Viewing the list of notification destinations
On the workspace settings page, the **Notifications** section displays the list of notification destinations.
Notifications list that contains the workspace notification destinations
For each destination, the list includes:
* The name of the notification destination.
* The type of destination (email, Slack, or Teams).
* A description of the destination.
* Whether the destination is currently enabled.
* When the destination most recently received a notification.
### Creating a notification destination
To create a notification destination:
1. On the workspace settings, under **Notifications**, click **Add destination**.
Add Notification Destination panel to add a notification destination to a workspace
2. In the **Name** field, provide a name for the destination.
3. From the **Provider** dropdown list, select how the notification is delivered. The options are:
* Email
* Slack
* Microsoft Teams
4. Provide the notification details.
* For email, the email address that receives the notification.
* For Slack, the [webhook URL](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/).
* For Microsoft Teams, the[ webhook URL](https://support.microsoft.com/en-us/workflows/send-messages-in-teams-using-incoming-webhooks).
5. To have Fabricate send notifications to this destination, make sure that **Enabled** is toggled to the on position.
6. Click **Save**.
Fabricate sends a test notification to the destination.
### Editing a notification destination
To change the configuration of a notification destination:
1. In the destinations list, click the edit icon for the destination.
2. On the details panel, update the destination configuration.\
\
You cannot change the destination provider.
3. Click **Save**.
### Disabling and enabling a notification destination
In the destinations list, the **Enabled** column indicates whether the destination is currently enabled.
To enable the destination, toggle **Enabled** to the on position.
To disable the destination, toggle **Enabled** to the off position.
### Sending a test notification to a destination
To test the notification destination, in the destinations list, click the test notification icon for the destination.
### Deleting a notification destination
To delete a notification destination:
1. In the destinations list, click the delete icon for the destination.
2. On the confirmation panel, click **Delete**.
---
# 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.tonic.ai/fabricate/workspaces/workspace-notification-destinations.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.
