> For the complete documentation index, see [llms.txt](https://threadly.gitbook.io/threadly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadly.gitbook.io/threadly/sending-messages/message-privacy.md). # Message Privacy Settings Threadly’s per-message privacy settings give you control over who can see engagement data — click counts, form responses, and acknowledgements — for each individual message. These settings only affect Threadly’s analytics views, not the Slack message itself. *** ## Available Settings ### Hide from Team Analytics When enabled, this message will **not appear in the shared Logs view** accessible to all team members. Only the sender and workspace admins can see the message in analytics. **When to use:** * Sending a message to a sensitive audience (e.g., HR or executive announcements) * Testing a workflow before rolling it out broadly * Messages with engagement data you prefer not to share team-wide ### Restrict Who Can View Details When enabled, you define an **approved-viewers list** — a specific set of team members who can view detailed engagement data for this message. Anyone not on the list will see the message in Logs but won’t be able to drill into individual user-level data. **When to use:** * Limiting access to form responses that contain personal or sensitive information * Restricting click analytics to relevant team leads only * Complying with internal data access policies *** ## How to Configure Both settings are available in the message composer: 1. While composing a message, look for the **Privacy** section (or the lock icon in the toolbar). 2. Toggle **Hide from team analytics** to prevent the message from appearing in shared Logs. 3. Toggle **Restrict viewers** and select the specific team members who should have access. 4. Complete your message and send. Privacy settings apply only to the message being composed. Each message can have different privacy settings. *** ## See Also * [Using Logs & Analytics](/threadly/analytics/using-logs-and-analytics.md) — how the shared Logs view works * [Message Acknowledgements](/threadly/sending-messages/message-acknowledgements.md) — require recipients to confirm they’ve read your message * [How Threadly Tracks CTA Clicks](/threadly/analytics/how-threadly-tracks-cta-clicks.md) — click tracking details --- # 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://threadly.gitbook.io/threadly/sending-messages/message-privacy.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.