> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/dashboard-v1.0/commons.md).

# Commons

## Context 

This is an Umbrella story for MUKTA Dashboard. Gives high level description details along with standard components. 

V1 Dashboard has 25 KPIs - 8 Simple numbers and 17 in Charts Design

### Standard components on dashboard

### Date Filter

### District Filters 

1. Should filter the dashboard data by selected District.
2. Multi select should be enabled.

### ULB Filters 

1. Should filter the dashboard data by selected District.
2. Multi select should be enabled.
3. Should be drilled down from District that is selected.

### Denomination

1. Cr, Lac, Unit as per DIGIT standard
2. Share
3. Email, Whatsapp as per DIGIT standard

### Download

1. JPEG as per DIGIT Standard 

## Roles

1. Define a single role called “MUKTA Dashboard Viewer” whoever has that access should have Dashboard link on left navigation menu and home page card links.
2. Use same dashboard Icon as per DIGIT standard.
3. Clicking on link will land user directly on dashboard Home with no filters applied. 

## User Acceptance

1. All filters, Denominations, Share and Download options to work as standard and expected.
2. All Cards will by default have menu individually(three dots). This will download image or share that card in that visualization to JPEG (Default DIGIT behavior)


---

# 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.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/dashboard-v1.0/commons.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.