# Masters List

## Overview

The complaints service appends to and modifies existing platform service masters for RBAC, ID formats, etc, and also defines its own.

## Masters

### Common Masters

<table><thead><tr><th width="226.50390625">Module</th><th width="154.015625">Master</th><th>Purpose</th></tr></thead><tbody><tr><td><code>ACCESSCONTROL-ROLES</code></td><td><code>roles</code></td><td>Defines user roles (e.g., <code>CITIZEN</code>, <code>PGR_LME</code>, <code>PGR_GRO</code>)</td></tr><tr><td><code>ACCESSCONTROL-ACTIONS-TEST</code></td><td><code>actions-test</code></td><td>Lists API actions such as <code>_create</code>, <code>_update</code>, <code>_search</code></td></tr><tr><td><code>ACCESSCONTROL-ROLEACTIONS</code></td><td><code>roleactions</code></td><td>Maps roles to actions (i.e., role-based API access control)</td></tr><tr><td><code>common-masters</code></td><td><code>IdFormat</code></td><td>ID generation rules (e.g., Complaint ID format)</td></tr><tr><td><code>tenant</code></td><td><code>tenants</code></td><td>List of tenants (e.g., <code>state.citya</code>)</td></tr><tr><td><code>tenant</code></td><td><code>citymodule</code></td><td>Defines which services are enabled for each city/tenant</td></tr><tr><td><code>common-masters</code></td><td><code>Department</code></td><td>List of departments (used for routing complaints)</td></tr></tbody></table>

### Masters Defined By CMS Service

<table><thead><tr><th width="213.46484375">Master </th><th>Purpose</th></tr></thead><tbody><tr><td><code>ServiceDefs</code></td><td>Defines complaint types and subtypes</td></tr><tr><td><code>UIConstants</code></td><td>Configures UI behavior (e.g., SLAs, rules for re-opening tickets)</td></tr></tbody></table>

### UI Masters

<table><thead><tr><th width="213.46484375">Master </th><th>Purpose</th></tr></thead><tbody><tr><td><code>GenderType</code></td><td>Defines user gender types in the Profile &#x26; user creation</td></tr><tr><td>StateInfo</td><td>Base configuration holds the languages, Banner, logo, background image URLs shown in the web UI. The URLs usually point to a S3 assets bucket.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digit.org/complaints-management/complaints-resolution-v2.10/design/architecture/masters-list.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.