> 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/data-library/infrastructure/dashboard-actions.md).

# Dashboard Actions

The **Dashboard Actions** section helps you manage your infrastructure systems from end to end. Whether you’re integrating cloud providers, assigning owners, classifying entities, or resolving compliance checks, this section provides step-by-step guidance on all actions available within the Infrastructure dashboard in Sprinto.

Use the links below to learn how to perform each task in detail.

***

### Available Actions

#### 1. Set Up Infrastructure Services

Learn how to integrate cloud service providers like AWS, Azure, GCP, Oracle Cloud, and more. Understand system syncing, connection health, and supported configuration steps.

#### 2. Update API Keys for Active Integrations

Rotate API credentials for integrated infrastructure systems without interrupting syncing or losing configuration. Currently supported for Azure and GCP.

#### 3. Assign Infra Owners

Assign or change the owner responsible for an infrastructure system’s compliance tasks. Infra Owners receive check notifications and handle resolution workflows.

#### 4. Classify Infrastructure Entities

Classify entities as *Production*, *Not Production*, or *Unclassified* using one of four methods: system-wide, manual, tag-based, or parent-based classification.

#### 5. Manage Non-Integrating Infrastructure Providers

Set up workflow checks to track compliance for infrastructure providers that aren’t directly supported by Sprinto integrations.

#### 6. Add and Configure Workflow Checks

Add checks from templates, create custom checks, or bulk upload workflow checks to validate encryption, backups, CPU monitoring, and other security controls.

***

### Additional Actions Within the UI

While not tied to individual articles, the following actions are accessible through the Infra systems dashboard:

<table data-header-hidden><thead><tr><th width="294.1796875"></th><th></th></tr></thead><tbody><tr><td><strong>Action</strong></td><td><strong>Where to Access</strong></td></tr><tr><td>View synced infrastructure entities</td><td>Infra systems > Click into any system</td></tr><tr><td>Open task drawer for a failing check</td><td>Click <em>Configure</em> > View resolution drawer</td></tr><tr><td>Change default classification</td><td>Infra systems > Configure</td></tr><tr><td>Set up capacity monitoring</td><td>Infra systems > Configure > Capacity monitoring</td></tr><tr><td>Monitor check statuses</td><td>Monitoring tab</td></tr></tbody></table>

***

### Next Steps

Once you’ve completed setup and classification, continue to the [**Monitoring**](/monitoring/overview.md) tab to track check statuses, resolve issues, and maintain ongoing compliance.

Let me know if you’d like a compiled export or want to proceed with **What’s New** or final indexing next.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinto.com/data-library/infrastructure/dashboard-actions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
