> 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/tenant-management.md). # Tenant Management ## Overview Tenant Management is the section in the Management Console that groups everything related to the tenant's core identity and its underlying structural masters — the things that were originally set up during Onboarding (Phases 1–2), now editable on an ongoing basis. ## Manage Tenant Data The different tenant data can be modified and updated as required from this console. The console contains the following five items:

Item	What it does
Tenants	Lists every tenant registered under your root account (e.g. every city under ‘ke’) - the same registry that powers "Use existing tenant" in the Onboarding wizard.
Departments	Create/edit departments for the tenant (e.g. Environment, Building & Roads)
Designations	Create/edit job titles, each linked to one or more departments
Hierarchies	View/manage the boundary hierarchy structure - e.g. Bomet County's real structure is County → SubCounty → Ward
Map Configuration	Controls how boundaries render on the map view

### Tenants The master registry of every account under your root tenant (e.g., every city under ‘ke’). Every complaint, every employee record, every boundary and every role assignment in the system belongs to exactly one tenant, and the system uses that ownership to keep accounts apart. Two cities (registered as two accounts) running on the same installation never see each other's data, because every record carries the tenant it belongs to. This page is the master registry of those cities. If a city is not listed here, it does not exist as far as the rest of the console is concerned.

Column	What it tells you
Code	The permanent identifier, in the form root.cityname (for example ke.bomet). This is the tenantId that every complaint, employee and boundary record points back to.
Name	The tenant's display name, shown to staff and citizens. A row where the Name looks like a code has simply never had a proper name set.
City	The city name held on the tenant's city record.
District	The parent district the city sits under. Used for grouping and for regional reporting.

Each row entry of a tenant holds information such as Contact details (Helpline number and email address) and address.

### Departments & Designations These define the organisational labels where an employee and/or complaint is bucketed into. A department is the organisation department to which an employee belongs in the government and also the primary point of accountability for a certain complaint. A Designation is what an employee is called. {% hint style="info" %} Note that these constructs don't define what a person does within the CMS platform. Permissions for a given action come from Roles, which are configured elsewhere. {% endhint %} Within the Department Section:

Field	What it is
Code	The permanent identifier of a department. Complaint types and employee records point to this value. Example: PWD_DEP
Name	The human-readable name shown throughout the console. This is what staff and reports actually see. Example: Public Works Department
Status	Whether the department is in use and active. Example: Active

Field

What it is

Code

The permanent identifier of a department. Complaint types and employee records point to this value.

Example: PWD_DEP

Name

The human-readable name shown throughout the console. This is what staff and reports actually see.

Example: Public Works Department

Status

Whether the department is in use and active.

Example: Active

These fields aid in defining complaint types as well as Employee information

Designations are descriptive. They appear on the employee record, in the staff organisation chart, and in reports. The system does not use them to run any actionable flow in the backend.

Field	What it is
Code	The permanent identifier for a designation.
Name	The job title as displayed.
Description	Free text description of the job title.
Status	Whether the designation is available and still valid.. (Active or Not)

### Hierarchies This section defines the **geography levels** your city or county is broken into. For example, County → SubCounty → Ward is a 3-level hierarchy that can be defined. Every complaint, employee assignment, and boundary record in the system is tagged against one of these levels, so this section decides how granular that tagging can get.

Field	What it is
Hierarchy type	Identifier for a hierarchy structure defined.
Tenant	Which tenant/city this hierarchy belongs to
app.fields.levels	The ordered list of boundary levels inside that hierarchy — e.g., County → SubCounty → Ward

Opening a hierarchy record also shows an additional “Audit” header where you will be able to see when the particular hierarchy was created, and the last modified date and by whom. If you see **System** here, it means that this was created during onboarding. You come to this section when your organisation's structure changes (e.g., a new administrative tier is introduced by government policy). Usually not for everyday data entry, which happens in the Boundary data itself once the hierarchy shape is locked in. ### Map Configuration This section controls the map itself - not what geography exists (that happens in Hierarchies), but how the map looks and behaves when staff open it: which map style loads, how far someone can zoom in or out, and where the map is centred by default.

Field	Section	What it controls
Code	Key	The record identifier.
Default Zoom	Additional	How close in the map is when it first loads.
Min Zoom	Additional	How far out a user is allowed to zoom.
Max Zoom	Additional	How far in a user is allowed to zoom.
Tile Url	Additional	Where the map imagery comes from.
Tile Attribution	Additional	The credit line shown over the map for the imagery provider.
Base Map Theme	Additional	The visual style of the base map, such as light or dark.
Boundary Tenant Id	Additional	Which tenant's boundaries to draw.
Ward Highlight Color	Additional	The colour used to mark a selected ward, as a hex value.
Geocode Country Codes	Additional	Restricts address search to specified countries.
Center	Nested data	The point the map opens on.
Search Viewbox	Nested data	The geographic box that address search is confined to.

Centre defines the point where the map is positioned when it loads, given as latitude and longitude: Example: `{` `"lat": -0.701337,` `"lng": 35.300323` `}` Set this near the middle of your geographic boundary (Example: Centre of your municipality). If it is wrong, every user begins by dragging the map before they can do anything. Search Viewbox defines the rectangle that address search results are confined to, given as four values: Example: `{` `"maxLat": -0.297315,` `"maxLon": 35.645467,` `"minLat": -1.105358,` `"minLon": 34.955179` `}` The box should enclose your whole jurisdiction with a small margin. --- # 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/tenant-management.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.