> 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/request-management/public-vs-private-requests.md). # Public vs Private requests Public requests keep the conversation in the Slack or Teams channel so others learn from the answer. Private requests move it to a DM for HR, security, and sensitive work. Some work benefits from visibility; other work demands confidentiality. Siit supports both modes so you can match the tone and sensitivity of each team. Public requests keep their conversation thread in the original Slack or Teams channel, which is perfect for an #it‑help channel where others can learn from the answer. Only the requester, participants, and authorized agents can act on the request, but the thread is discoverable in that channel for transparency. Private requests move the conversation to a direct message with the requester and the Siit App. Only the requester, explicitly added participants, and authorized agents can see the conversation. This is ideal for HR, Security, or anything sensitive that started in a public channel by mistake. Admins can set the default mode by channel, by catalog item, or by team. Approvals are always presented privately to the approver, regardless of request mode. Reporting treats both modes the same, so your metrics stay comparable. #### Best practices Public requests are often the first place for internal support. Examples include: * `#ask-it` * `#help-people` * `#feedback-product` \ Private request: Feels personal, stays organized Private requests in Siit don’t go to an agent’s personal DMs.\ Instead, teammates message the Siit app. To the requester, it feels like a one-on-one conversation. For agents, it keeps personal inboxes clear and ensures all requests flow into the right workspace queue. *** ### Siit supports both Siit gives you the advantages of each model without forcing your team to pick one. #### In public channels * Turn any message into a request with a shortcut or emoji * Siit creates a thread and tracks it as a structured request * Multiple responders can collaborate without cluttering the channel * Requesters get automatic updates as progress is made #### In private DMs * Requests can be submitted directly to the Siit App * Sensitive issues stay private but are still tracked in the workspace * Agents manage all requests from one Workspace, whether they start in a channel or a DM *** Siit adapts to how your team already works and makes support smoother across both public and private conversations. --- # 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/request-management/public-vs-private-requests.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.