> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/trust/trust-center/dashboard-actions/trust-center-requests-in-slack.md).

# Trust Center Requests in Slack

Manage Trust Center access requests directly in Slack without switching to the Sprinto app.

The Trust Center allows organisations to share security and compliance documents with external stakeholders while maintaining control over sensitive information. Documents marked as restricted require admin approval before access is granted.

With Slack notifications enabled, Sprinto sends real-time alerts to admins whenever an external user requests access to a restricted Trust Center document. Admins can review the request details and take action directly from Slack, with all decisions automatically synced back to Sprinto.

***

### Prerequisites

Before using Slack-based approvals for Trust Center documents, ensure that:

* You have **admin access** in Sprinto.
* Slack notifications are enabled for your workspace. Know more about [how to enable Slack notifications](https://docs.sprinto.com/settings/notifications.md#slack-notifications-and-approvals).
* Restricted documents are configured in the Trust Center.
* Admins responsible for approvals are added under **Trust Center → Team**.

***

### How the request and approval flow works

#### Step 1: External user views the Trust Center

* An external user opens your Trust Center website.
* They can view all publicly available resources and documents.
* Restricted documents are visible but require approval to access.

***

#### Step 2: External user requests access to a document

1. The user navigates to the **Resources** section of the Trust Center.
2. Next to a restricted document, the user selects **Request access**.
3. A request drawer opens where the user:
   * Confirms their work email
   * Enters their name and company
   * Selects a reason for requesting access (existing customer, prospective customer, or other)
4. The user submits the access request.

Once submitted, the requester sees a confirmation that access has been requested and will be notified once the request is approved or rejected.

***

#### Step 3: Admins receive a Slack notification

* Sprinto sends a Slack notification to the configured workspace.
* All admins listed under **Trust Center → Team** receive the request.
* The notification includes:
  * Requester details
  * Document name
  * Action buttons to approve or reject the request

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FUXVmethkEfBJ1ZDBv6RW%2FScreenshot%202026-02-03%20at%2017.00.29.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

***

#### Send requests and decisions to a shared Slack channel

By default, Trust Center Slack notifications go to each admin individually, as direct messages. If your team triages access requests together, you can also route them — and every decision made on them — to one or more shared Slack channels, so nothing waits in a single person's inbox.

**To turn on a shared channel:**

1. Go to **Settings → Notifications**.
2. Open the **Trust Center** row.
   * On the current Notifications page, this opens the Trust Center drawer; under the **Slack** row, switch on **Send to a common Slack channel**.
   * On the new Notifications page, open the **Trust Center** area, then use its **⋮** menu to select **Common Slack channel**.
3. Under **Select Channels**, choose one or more Slack channels. You can select multiple channels to broadcast notifications.
4. Select **Save Changes**.

![The Trust Center notification drawer in Sprinto's legacy Settings > Notifications page, showing the Email and Slack rows. Under Slack, a "Send to a common Slack channel" toggle (tagged New) is switched on, with a Select Channels field showing the #trust-center-updates channel selected and a hint reading "You can select multiple channels to broadcast notifications." The toggle section is boxed in red.](https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FRu7yJNJuImpVdaJw5na9%2FS1-v3-drawer.png?alt=media)

![The new Sprinto Notifications settings page with the Trust Center area expanded. A dropdown menu opened from the area's ⋮ (kebab) button shows two options, "Common Slack channel" and "Disable all notifications." The "Common Slack channel" menu item is boxed in red.](https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2F05DCqkTZEoctUcFid1ZF%2FS2-v4-kebab-menu.png?alt=media)

![The "Common Slack channel" modal opened from the Trust Center area on Sprinto's new Notifications settings page. It shows the "Send to a common Slack channel" toggle on, a Select Channels field with #trust-center-updates selected, the hint about broadcasting to multiple channels, and Cancel / Save changes buttons. The Select Channels control area is boxed in red.](https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FTk6VpGb7zZvpiu1xPZKC%2FS3-v4-modal.png?alt=media)

Once a channel is on, the following post to it, once per event:

* New access requests.
* Every decision made on a request — approved, approved with NDA, or rejected — including requests that were approved or rejected automatically by a rule.

Each decision post shows who decided: the admin's name, or "Automatic" when a rule made the call. The rejection reason is never posted to the channel.

{% hint style="info" %}

#### Note

Channel posts are **in addition to** each admin's individual Slack notifications — turning on a shared channel never stops an admin's own DMs or emails.
{% endhint %}

***

#### Step 4: Admin approves or rejects the request from Slack

* Admins can select **Accept request** or **Reject** directly in Slack — from their own notification, or from a shared channel if one is configured.
* The action is processed immediately, and any other shared channel is updated to show the decision.
* Sprinto updates the request status in the Trust Center automatically.

Admins can also use the **View in Sprinto** option if they want to review the request in the dashboard.

***

### What happens after the request is processed

* **If approved**:
  * The external user gains access to the requested document.
  * The requester is notified that access has been granted.
  * The request status is marked as approved in Sprinto.
* **If rejected**:
  * The external user is notified that access was denied.
  * The decision is logged in Sprinto for audit and tracking purposes.

***

### Key notes

* Only users added under **Trust Center → Team** receive individual Slack notifications for access requests.
* Slack approvals work only when Slack notifications are enabled and connected.
* A shared Slack channel for Trust Center is optional, and separate from the shared channel used for task notifications — turning one on or off never changes the other.
* Shared-channel posts are additional to each admin's individual DMs and emails; nothing is replaced.
* If a configured channel stops working (for example, the Sprinto bot is removed or the channel is archived), admins still get their individual notifications — no request is lost.
* Can't find a private channel in the picker? Invite the Sprinto bot with `/invite @Sprinto`, then select **Refresh**.
* All approval actions taken in Slack are reflected in real time in the Sprinto dashboard.
* Admins can still manage access requests directly from Sprinto if needed.


---

# 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.sprinto.com/trust/trust-center/dashboard-actions/trust-center-requests-in-slack.md?ask=<question>&goal=<user_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.
