> 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/audits/evidences/dashboard-actions.md). # Dashboard Actions Here’s a concise, **overview-style draft** for the **Dashboard Actions** main page in the *Evidences* section, following the **Microsoft Writing Style Guide** and using **British English**: *** ## Dashboard Actions The **Dashboard Actions** section helps you perform key evidence management tasks directly from the Evidences dashboard. Whether you're uploading files, assigning metadata, requesting evidence, or tracking review progress—this is your operational hub for handling evidence in Sprinto. You can access all evidence types—**Automated**, **Uploaded**, **Workflow**, **Requested**, and **Policy**—through a unified table interface, enabling efficient filtering, bulk actions, and real-time tracking. *** ### What you can do The Dashboard Actions are grouped into three main categories: #### Create Add evidence to Sprinto in the following ways: * Upload files or links individually or in bulk * Create single or CSV-based evidence requests #### Manage Organise and update your evidence by: * Editing metadata fields and custom tags * Mapping evidence to controls or audits * Managing archived or versioned items #### Complete Finalise evidence-related workflows by: * Uploading evidence against requests * Reviewing submitted items * Attaching evidence to audit requirements *** ### Why it matters Having your evidence on the platform is a prerequisite for running audits on Sprinto. The Dashboard Actions interface ensures that evidence is: * Easily uploadable and requestable * Fully versioned and traceable * Mapped to compliance controls and audit items * Filterable and editable at scale *** ### Tip Use metadata fields like *Evidence group*, *Collected date*, and *Custom tags* to organise your evidence better and locate files faster during audits. --- # 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/audits/evidences/dashboard-actions.md?ask=&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.