> 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.md).

# Dashboard Actions

Here’s the **Dashboard Actions – Overview** page for the **Controls** section, written to match the style we’ve used for other Compliance documentation.

***

**SEO Description:**\
View all dashboard actions available in the Sprinto Controls section, including adding new controls and managing existing ones.

## Dashboard Actions – Overview

The **Dashboard Actions** in the Controls section allow you to create, import, and maintain controls to match your organisation’s compliance requirements. These actions give administrators the flexibility to add new controls, update existing ones, and ensure that each control is mapped to the right checks and frameworks.

### Available Actions

<table><thead><tr><th width="162.83203125">Action</th><th>Description</th></tr></thead><tbody><tr><td><strong>Add Controls</strong></td><td>Create a new control manually or add multiple controls in bulk using the CSV template. Define control details, assign ownership, and link them to relevant compliance domains.</td></tr><tr><td><strong>Manage a Control</strong></td><td>Update control details, map or unmap checks, disable controls, and manage associated frameworks and criteria to keep compliance coverage accurate and current.</td></tr></tbody></table>

### Why These Actions Matter

Controls are the foundation of your compliance framework in Sprinto. Having the ability to create and manage them directly from the dashboard ensures:

* Compliance requirements are well-defined and documented.
* Controls remain aligned with operational and regulatory changes.
* Framework and criteria mapping is always accurate.
* Monitoring checks are relevant and effective.

By using these dashboard actions effectively, you can maintain a strong, clear, and up-to-date compliance posture across your organisation.


---

# 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.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.