> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-communication/slack-private-notes.md).
# Add private notes from Slack
Add a private note to a request from Slack by starting your message with the lock emoji in the admin notification, synced as an internal comment visible to admins only
Admins can easily add private notes to requests directly from Slack. These notes are crucial for internal communication. By using this feature, admins can keep their internal discussions organized and secure, enhancing both communication and efficiency within the team.
⚠️ Private notes in Slack are only visible to admins who have access to the admin notification of the request.
### How to Add a Private Note
To add a private note from Slack, use the 🔒 emoji in the Admin notification. The message can be placed at either the start of your message. This enables Siit to automatically identify and convert the message into a private note.
These private notes will be synced as internal comments to the request conversation.
Feel free to read another article on how to leverage emojis in Slack to perform various actions.
---
# 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.siit.io/guides/integrations/integrations-communication/slack-private-notes.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.
