> 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/compliance/controls/dashboard-actions/add-controls.md).

# Add Controls

Add a new control in Sprinto manually or in bulk using the CSV template to define and track compliance requirements effectively.

In Sprinto, you can add new controls to define specific compliance requirements for your organisation. Controls can be created one at a time or imported in bulk, depending on your needs.

Adding controls ensures that compliance obligations are clearly documented, assigned to the right owners, and linked to relevant monitoring checks and frameworks.

### Add a Single Control

1. Log in to the Sprinto dashboard and navigate to **Compliance > Controls**.
2. Click **Add New Control** and select **Add Control**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2Fbd69Mp6bygHyhDSYlreG%2FScreenshot%202025-10-27%20at%2014.30.26.png?alt=media&amp;token=536da685-f25c-40e2-a3fe-dfb2c37a9e7d" alt="" width="563"><figcaption></figcaption></figure>

3. Enter the following details:
   * **Control Number** – Unique identifier for the control.
   * **Control Name** – Short, descriptive title.
   * **Description** – Detailed explanation of the control’s purpose.
   * **Control Owner** – The person responsible for implementing and maintaining the control.
   * **Domain** – The relevant compliance domain or category.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FYvpqbhykckKralxwlvzz%2FScreenshot%202025-10-27%20at%2014.32.22.png?alt=media&amp;token=e0a5e36b-a1f1-4336-944b-f361fc6c1ee6" alt="" width="563"><figcaption></figcaption></figure>

4. Click **Create Control** to save the control. The new control will appear in the **Enabled** tab.

### Add Controls in Bulk

1. Log in to the Sprinto dashboard and navigate to **Compliance > Controls**.
2. Click **Add New Control** and select **Bulk Import Controls**.
3. Click **Download this Template** to download the CSV file.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2Fp5kHSaf1KHAiNKshm5aK%2FScreenshot%202025-10-27%20at%2014.34.39.png?alt=media&amp;token=e5be6b06-ff19-4402-afd6-3f0d96386718" alt="" width="375"><figcaption></figcaption></figure>

4. Fill in the required fields in the template, such as:
   * **Control Number**
   * **Domain**
   * **Control Name**
   * **Control Description**
   * Applicable framework mappings (for example, SOC2 Security, SOC2 Availability, HITRUST).
5. Save the completed CSV file and return to Sprinto.
6. Upload the file to the bulk import section and click **Preview controls**.
7. Preview the imported controls to verify accuracy.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FvHj4d3nw1bAXj17xDWNP%2FScreenshot%202025-10-27%20at%2014.36.58.png?alt=media&amp;token=2dedbd6a-fa60-4e14-9f1e-cf8441f6ba90" alt="" width="563"><figcaption></figcaption></figure>

4. Click **Add Control** to complete the import.

Once added, you can manage these controls by linking them to checks, mapping them to frameworks, or updating their details as 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/compliance/controls/dashboard-actions/add-controls.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.
