> 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/management-admin-console.md). # Management Admin Console Console layout ## Overview The Management Console is the day-to-day administration screen for an account that has already been onboarded. Unlike the four-phase Onboarding wizard (used once to set up a new city), the Management Console is a full CRUD interface you come back to any time you need to add a department, fix an employee record, review a workflow, or check on notification delivery. ## Layout The left sidebar stays fixed and is grouped into: **Dashboard, Public Dashboard, Notifications, Tenant Management, Complaint Management, People, System,** and **Advanced**. Every screen also shows: * A **"Management Mode"** badge, top-left, showing your current working context * A documentation panel, right side, linking to relevant DIGIT docs to refer to for a deep dive.
**Switch to Onboarding:** Click the **Switch to Onboarding** button, bottom-left of the left navigation bar. **Common buttons across the Management Console:** * **Refresh** — re-fetches the tenant list from the backend. Without it, you are just seeing the data loaded when you logged in. * **Edit -** the edit button allows you to modify or update the data. * **Export** — downloads everything currently set up as a spreadsheet, so you can review or edit it outside the console. Best for bulk changes (e.g. adding 50 new wards or 15 designations) — Export gives you the full existing list first, so you're editing on top of it rather than starting blank and risking missed rows. * **Bulk Import** — uploads a spreadsheet to add or update many records at once, instead of filling out forms one by one. Best for batch jobs like restructuring a large chunk of records. --- # 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/management-admin-console.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.