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

# Settings

## Notification Settings

#### **Setting Slack Member ID**

You can receive slack notifications for test run status changes (when a test run gets submitted and completes) and when a team member leaves a message on a test run. You can choose to receive a notification to your email, a Slack DM or both.

Once these notifications are turned on, all manual test runs will default to that setting. You have the option to turn them off/on at the time you manually start a test run.

In Testery, go to Settings --> Profile tab. You will see the following notification settings.

![Testery Notification Settings](/files/XBcxbFUMWjdSHIm0Zbmr)

Turn on email or slack notifications or both. If you turn on Slack notifications you will need to connect your Slack user to your Testery User. To do this...

1. Ensure your Slack Workspace is authorized. In the Testery App, go to Settings > Integrations. If you see, "Authorize Slack Integration," click that and complete that process.
   * If you see "Remove Slack Integration," then you are already authorized and can move forward.
   * This only needs to be done once in your Testery account.
2. In Slack, type the command `/testery connect`. Follow the prompts to complete the process and your users will then be connected.
   * Each Testery user that wants/needs Slack notifications must also use the `connect` Slash Command above.

{% hint style="info" %}
If Slash commands aren't working, you may need re-install your Slack App...

1. Go to Settings > Integrations
2. Click the "Remove Slack Integration" button. Complete the process.
3. Click the "Authorize Slack Integration" button. Complete the process.
   {% endhint %}

{% hint style="info" %}
These settings only apply to test runs kicked off manually. If there is a particular test run that is scheduled that you would like to follow, you would have to go into the test run once its activated and follow the test run.
{% endhint %}


---

# 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.testery.io/get-to-know-testery/settings.md?ask=<question>&goal=<endgoal>
```

`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.