> 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/complaints-management/access/configurator-management-guide/dashboard.md). # Dashboard This is the landing page of the Management Console — **DIGIT Management Studio** — which shows a live count for every major registry in the tenant: Tenants, Departments, Designations, Complaint Types, Employees, Boundaries, Complaints, Localisation Messages, Users, and Access Roles.

Tiles	What it represents
Tenants	Number of tenant accounts registered under your root (e.g. city/ULB accounts under ‘ke’)
Departments	Number of departments configured (e.g. Environment, Building & Roads)
Designations	Number of job titles/roles-within-department configured
Complaint Types	Number of complaint categories citizens can file against
Employees	Total staff accounts in HRMS
Boundaries	Total geographic area records (wards, localities, etc.)
Complaints	Total complaints filed on this tenant - 0 on a tenant with no citizen activity yet
Localization Messages	Total translated UI strings for this tenant
Users	Total login accounts — both employee and citizen
Access Roles	Total roles defined on the platform (e.g. SUPERUSER, GRO, CSR)

--- # 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/complaints-management/access/configurator-management-guide/dashboard.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.