> 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/handle-access-requests-and-data-rights-submissions.md).

# Handle Access Requests and Data Rights Submissions

Learn how to manage document access requests and handle data rights submissions through your Sprinto Trust Center.

Sprinto’s Trust Center not only showcases your security posture—it also enables you to handle inbound requests securely and transparently. This includes both access requests to restricted documents and data rights submissions aligned with privacy regulations like GDPR or CCPA.

This article explains how to manage these two key workflows.

***

### Access Requests

#### View and Respond to Requests

1. Navigate to the **Access Requests** tab.
2. You’ll see a list of all access requests made through your Trust Center.
3. For each request, review:
   * Requestor name and email
   * Requested documents
   * Time of request
   * NDA status (signed or pending)

#### Take Action

* **Approve** to grant document access
* **Reject** to deny the request
* **Request More Info** if clarification is needed

The requestor will receive a notification based on your action.

{% hint style="info" %}
Access validity is determined by the duration configured in the NDA settings (e.g., 7 days).
{% endhint %}

***

### Data Rights Requests

#### Access the Tab

1. Click on the **Data Rights Requests** tab.
2. View all submissions made by end-users related to:
   * Data export
   * Data deletion
   * General privacy requests

#### Manage the Request Form

1. Click **Manage Data Requests Form** on the top right.
2. A drawer opens showing all available fields.
3. You can:
   * Enable/disable predefined fields
   * Add custom fields via **Add Custom Field**
   * Modify placeholder text and descriptions
   * Change the order of the fields — drag a field by its handle in the **Form fields** list to the position you want. You can also move a field with your keyboard.
4. Click **Save form** to keep your changes. Closing the drawer without saving discards them.

Visitors see the fields on your Trust Center data request form in the order you save.

{% hint style="info" %}

* **Name**, **Email ID** and **Request type** can be moved like any other field, but they are always shown and always required.
* Only fields marked Required are shown on the form.
* New custom fields are added at the bottom of the list. If you deactivate a custom field, it is removed from the list and the remaining fields keep their order.
  {% endhint %}

All submissions are visible in the tab with the corresponding field data filled in.

***

### Best Practices

* Respond to access requests within your standard SLA.
* Configure NDAs and document visibility rules to align with request workflows.
* Monitor trends in request types for privacy audits.

***

Managing these requests through a central interface ensures a streamlined experience for both internal stakeholders and external visitors.


---

# 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/handle-access-requests-and-data-rights-submissions.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.
