> 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/cms-v2.11/access/configurator-management-guide/glossary.md). # Glossary Glossary of terms

S.No.	Term	Definition
1	CMS	Complaint Management System
2	Admin Console/ Configurator	The tool an admin uses to set up and manage a city's account in the Complaints Management System. Note: Both of these terms have been used interchangeably in this document
3	Account or Tenant	A tenant is the main "account" for one organization using the CMS - typically a state, country, or governing body. Everything created under this account - its cities, staff, settings, and data, stays contained within it and is kept separate from every other account on the same system.
4	Sub-Account or Sub-Tenant	A sub-tenant is a smaller account that sits inside a main account - usually representing one specific city or local body belonging to that state/country. It automatically picks up the basic setup from its parent account, but its own day-to-day data (complaints, staff, local boundaries) is kept separate from other cities under the same parent.
5	Root Tenant	The top-level account in the system, usually representing a whole state or country (e.g., mz for Mozambique, pg for Punjab).
6	Master Data	The core reference information, including standard lists and categories
7	MDMS	Short for Master Data Management Service - the part of the system responsible for storing and managing all the master data described above. It works like a central rulebook or reference library: every screen and feature in the system checks MDMS to know what options (departments, complaint types, roles, etc.) it should show.
8	SUPERUSER	Top-level admin role. This role can create other users, change settings, manage master data, and oversee day-to-day operations, etc. It's the broadest level of control a single account offers.
9	MDMS_ADMIN	An administrator role focused specifically on managing master data - someone who can add, edit, or update the reference lists stored in MDMS (departments, job titles, complaint types, etc.). It's narrower than SUPERUSER: this role controls how the system works, not the account as a whole.

--- # 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/cms-v2.11/access/configurator-management-guide/glossary.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.