> 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/management-console-guide.md).

# Management Console Guide

## Overview&#x20;

The Configurator is where you set up and manage everything about your account's Complaint Management System- without needing a developer. You use it once to onboard a new account, and then keep coming back to it to manage departments, staff, complaint categories, escalation, notifications, and more, as things change.

It runs entirely in your browser and talks directly to the DIGIT platform, so there is nothing to install.

## Get Started

1. Open the Complaint Management Configurator and click Log in. You sign in on the DIGIT sign-in page with your email address and password.
2. First time, or forgotten your password - Use Set up or reset your password to get an email link. New to DIGIT - Use Create an account to sign up for a new workspace.
3. If you belong to more than one workspace, pick one on Choose a workspace. Workspaces whose account is inactive or whose trial has ended are marked.
4. If the workspace has not finished onboarding, you are taken to the guided Onboarding Experience (refer to the [Onboarding user guide](https://docs.digit.org/complaints-management/access/account-creation-and-onboarding-guide.md)). Once every onboarding step is complete, you land in the Management Console.

Only admin roles can enter the console: SUPERUSER, ACCOUNT\_ADMIN, MDMS\_ADMIN, LOC\_ADMIN, HRMS\_ADMIN or WORKFLOW\_ADMIN. If your session expires, you're sent back to sign in with "Your session expired. Sign in again to continue."

## DIGIT Complaint Management Studio

The Complaint Management Studio is the day-to-day administration screen for an account that has already been onboarded. You come back to it any time you need to add a department, fix an employee record, change an SLA or check on the system.

### Layout

The Studio has a persistent left sidebar grouped into: Main (Dashboard, Public Dashboard), Notifications, Tenant Management, Complaint Management, People, System, and Advanced. Groups expand and collapse, and the rail itself can be collapsed.

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2FahMy3awoU88aJkgzzwOf%2FThe%20Management%20Studio%3A%20sidebar%20on%20the%20left%2C%20Workspace%20links%20and%20counts%20on%20the%20Dashboard?alt=media&amp;token=28986e81-6b0b-4447-86d9-637a389a5af4" alt="The Management Studio: sidebar on the left, Workspace links and counts on the Dashboard" height="293" width="600"></div>

<table><thead><tr><th width="210.1953125">Element</th><th>What it does</th></tr></thead><tbody><tr><td>Sidebar Search</td><td>Filters the menu by name so that you can jump to a screen. It does not search your data.</td></tr><tr><td>Management Mode badge</td><td>Top-left; confirms you are in the Management Console. A second badge shows the environment.</td></tr><tr><td>Help</td><td>Opens Help &#x26; Shortcuts: a quick guide plus keyboard shortcuts (Ctrl+/ or F1 opens help, Ctrl+Z undoes, Esc closes).</td></tr><tr><td>Theme</td><td>Changes the colour scheme of the console only. It does not change what citizens or employees see; for that, use Branding.</td></tr><tr><td>Account Drop down </td><td>Your name and workspace, plus Your account, Members (invite, re-invite and manage staff logins), Workspace settings (e.g. the account name), Open DIGIT Docs and Sign out.</td></tr><tr><td>Open complaint desk</td><td>Bottom of the sidebar; opens the Employee app in a new tab.</td></tr></tbody></table>

The box titled Workspace links on the Dashboard gives you the URLs of the Employee app (where staff sign in and handle complaints) and the Citizen app (share this with citizens to file and track complaints), each with Copy and Open.

#### Buttons you see on most screens

<table><thead><tr><th width="145.26953125">Button</th><th>What it does</th></tr></thead><tbody><tr><td>Refresh</td><td>Re-fetches the list from the server. Lists are otherwise cached for up to 5 minutes, so use Refresh after changes made elsewhere.</td></tr><tr><td>Create</td><td>Opens a blank form for a new record. Hidden if your role can't create that kind of record.</td></tr><tr><td>Export</td><td>Downloads the current list as a spreadsheet (.xlsx), so you can review it or edit it outside the console. Available on Departments, Designations and Localization.</td></tr><tr><td>Bulk import</td><td>Uploads a spreadsheet to add many records at once: download the template, fill it in, upload, preview, then import. Available on Departments, Designations, Employees and Localization.</td></tr><tr><td>Search / filters</td><td>Narrow the list, e.g. by Status or Department. Column headers sort the list.</td></tr><tr><td>A Row click</td><td>Opens the record's details page, with Edit at the top right.</td></tr></tbody></table>

There is no Delete button. To retire a record, edit it and switch Active off. Departments and Designations warn you how many designations or employees still depend on the record before you deactivate it. Record codes can't be changed after creation.

You may see a screen or button but still be refused on save: what the console shows is worked out in your browser from your roles, and the server makes the final check.


---

# 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/management-console-guide.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.
