> 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/release-notes.md).

# Release Notes

Release notes for DIGIT Complaint Management v2.20

{% hint style="info" %}
**Release Date - October 30, 2026**
{% endhint %}

## Release Summary

Complaint Management System (CMS) v2.20 adds self-serve workspace onboarding, a single sign-on service built on Keycloak, per-tenant notifications, and a redesigned citizen and employee experience. It also includes every v2.12.1 patch fix.

**Themes**

1. **Self-serve onboarding.** A government admin signs up, sets up its own complaint system in five guided steps, and starts taking complaints without eGov engineers.
2. **One sign-in for everyone.** Citizens, employees and administrators sign in through one secure service. People can belong to several workspaces.
3. **Better complaint handling.** Escalation follows the officer's reporting line, roles are standardised, and the citizen and employee screens are enhanced.
4. **Notifications per workspace.** Each workspace chooses its own SMS, email and WhatsApp providers and its own message wording.
5. **Security and safe operations.** More than 30 partner security-audit findings are fixed (six remain open), and an upgrade no longer leads to a wipe in the database.
6. **More languages and channels.** French and Portuguese are available out of the box; citizens can speak their complaint, and WhatsApp complaints are supported end to end.

#### At a glance

* **Upgrade path:** v2.12 → v2.20&#x20;
* **New services:** self-serve onboarding, single sign-in and more — see [New Services ](#new-services)for the complete, audited list&#x20;
* **Major feature:** A government admin signs up, sets up its own complaint system in five guided steps, and starts taking complaints without eGov engineers.

## Highlights

<table><thead><tr><th width="170.27734375">Change</th><th width="419.41796875">What it means</th><th>Who benefits</th></tr></thead><tbody><tr><td>Self-serve workspace onboarding</td><td>A new government signs up and sets up in five guided steps (Branding, Geography, Departments, Employees, Complaint types), then opens the complaint desk.</td><td>Administrators, partners</td></tr><tr><td>One secure sign-in</td><td>One sign-in for citizens, employees and admins, with invitations, sessions that stay alive while you work, and sign-out of other devices.</td><td>All users, security teams</td></tr><tr><td>Enhanced escalation</td><td>Complaints move up the officer's reporting line on time and once per level. Admins set the timings.</td><td>Citizens, officers, admins</td></tr><tr><td>Clearer complaint roles</td><td>Only the officer holding a complaint can escalate it. A Grievance Routing Officer assigns or rejects.</td><td>Employees</td></tr><tr><td>Redesigned citizen journey</td><td>File a complaint in three steps, with voice input. "My Complaints" works as an inbox.</td><td>Citizens</td></tr><tr><td>Redesigned employee console</td><td>New top bar and sidebar, tidier inbox search and filters, better on phones.</td><td>Employees</td></tr><tr><td>Notifications per workspace</td><td>Each workspace has its own message providers, wording and delivery logs.</td><td>Administrators, operations</td></tr><tr><td>French and Portuguese</td><td>Citizen and employee screens are available in French and Portuguese out-of-the-box.</td><td>Citizens, employees</td></tr><tr><td>Workspace trial (optional)</td><td>Partners can put new workspaces on a 30-day trial, with reminder emails before it ends.</td><td>Partners, operators</td></tr><tr><td>Readable on every theme</td><td>Text, field borders and focus outlines meet accessibility contrast standards on all themes.</td><td>All users</td></tr><tr><td>Security audit findings fixed</td><td>30+ audit findings fixed, including two high-severity ones; six remain open (section H). Plus hundreds of library vulnerabilities.</td><td>Everyone</td></tr><tr><td>Safer upgrades</td><td>An upgrade can no longer wipe an existing database.</td><td>Operations</td></tr></tbody></table>

## New Services

#### 1. Self-serve workspace onboarding

A city or organisation can sign up on its own and get a working complaint system. An admin creates an account, then goes through five guided steps: Branding, Geography, Departments, Employees and Complaint types (with a resolution time per category). When account setup is done, the Complaint Management Studio (also referred to as the 'Configurator') is displayed for any day-to-day admin updates. Employees get invitations, and admins can see whether each invite was accepted. Self-serve workspaces created earlier pick up new defaults in the background without losing their own changes; workspaces set up by the deployment itself are not upgraded this way. Sign-up is offered in English, French, Hindi and Portuguese, and, where the deployment has set up Google, admins can sign up with their Google account. This cuts the engineering work needed to launch a new account.

#### 2. One secure sign-in

Citizens, employees and administrators sign in through one secure service. A person can belong to several workspaces and pick one after signing in. Admins can invite people and resend activations; invitees can decline. Sessions end automatically when a person's credentials change, and otherwise stay alive while the person is active instead of ending 30 minutes after sign-in. Employees sign in with their email address and reset forgotten passwords by email, and "sign out other sessions" really signs out every other device. Existing staff must be linked to the new sign-in service before they can sign in (section F).

#### 3. Notifications per workspace

Each workspace can have its own SMS, email and WhatsApp providers, wording and delivery logs. Six providers are supported: Twilio SMS, Twilio WhatsApp, SMTP email, SMSCountry, Ozeki and Jasmin. Admins manage this in the Configurator under Notifications: Providers, Channels, Configure, Events, Logs and User Preferences. Templates are checked when saved, and Logs show whether each message was delivered.

#### 4. Citizen complaint filing with voice input

Citizens file a complaint in three steps and can speak the description instead of typing it. Voice works in English, French and Portuguese, and the screen shows which language it is listening in. "My Complaints" works as an inbox with search and paging.

#### 5. French and Portuguese out of the box

Citizen and employee screens ship in French and Portuguese out of the box.

#### 6. Complaints on WhatsApp

Citizens can file and track complaints over WhatsApp, in the workspace's own language and country code.

#### 7. Official boundaries for Geography setup

During setup, an admin can start from a country's pre-loaded administrative boundaries (if available) instead of drawing them. Each level shows the degree of validation of the data, and licences are tagged with the data. Chosen boundaries stay in an editable list until the admin saves. Google Maps can be used as the map, provided the admin brings their own Google API key.

#### 8. Escalation policy editor

Admins set when complaints escalate automatically, for example at 80%, 120% and 200% of a complaint type's resolution time, and can override it per complaint type.

#### 9. Workspace trial and reminder emails (optional)

A partner hosting many governments can put each new self-serve workspace on a 30-day trial. When a trial ends without approval, sign-in to that workspace pauses with a clear message, and an operator can approve or extend it. Workspace admins get reminder emails 14, 7, 3, 2 and 1 days before. Existing workspaces never lock.

#### 10. App links for staff and citizens

The Configurator dashboard shows copyable links to the workspace's employee and citizen apps, ready to share right after setup.

#### 11. Operations tools

* **Alerting (optional).** Alert rules and automatic investigation of alerts for single-server deployments.
* **AI incident diagnosis (optional).** An assistant that looks into incidents and reports findings, without making changes.
* **Per-container metrics.** CPU, memory and restarts for each part of the system.
* **Read-only automation tools.** The automation server can be shared publicly with write actions switched off.
* **Security scanning.** One scanner across the codebase, with a dashboard.

### UI/UX Enhancements

**Employee console**

* Enhanced Employee experience UI
* A workspace switcher for staff who work across workspaces.

**Citizen app**

* Enhanced Citizen experience UI
* Enhanced complaint filing flow
* Voice-enabled complaint description intake in EN, PT and FR.

**Public dashboard**

* Controls in the Configurator: status, preview, KPI list and access settings.
* KPI tiles show when the data was last refreshed, for example: "updated 5 minutes ago".
* The Add KPI list is searchable and sorted alphabetically, and the citizen app links to the dashboard.

**Configurator**

* A searchable time-zone picker, and a help panel, guided tour and short videos for each setup step.
* Branding changes can now be made in the Management Console.
* Additional notification configuration options, now at an account level.

**Analytics**

* Each workspace can send usage events to Matomo or PostHog, without sending PII.
* Each partner can use its own analytics and error-tracking accounts.

**Accessibility**

* Text, field borders and focus outlines meet colour-contrast standards on every theme. Contrast failures dropped from 31 to 0 on citizen pages and from 87 to 0 on employee pages.

**Quality**

* Automated tests run on every change, including a full journey from sign-up to a resolved complaint.
* The test dashboard keeps 30 runs and emails the team when something regresses.

## Fixes

About 55 fixes, grouped by area.

<table><thead><tr><th width="156.85546875">Area</th><th>What was fixed</th></tr></thead><tbody><tr><td>Escalation</td><td>Manual and automatic escalation now follow the same rule: the officer's reporting manager. A complaint type's own timings win over the default. Reopening keeps the escalation level. Escalate is hidden when there is nobody to escalate to.</td></tr><tr><td>Roles</td><td>A Grievance Routing Officer can only assign or reject. Assigning always names an employee.</td></tr><tr><td>Complaints</td><td>Assigned officers can always see their complaints. Complaints without a map pin no longer show a false location. Search never shows another tenant's complaints. A complaint filed by staff for a citizen now appears in that citizen's My Complaints. WhatsApp complaints show the real complainant. Labels, locked locations and category choices behave correctly.</td></tr><tr><td>Employees</td><td>New employees can file complaints. A failed invitation no longer creates a duplicate. Employee look-ups stay within the workspace. Adding an employee no longer fails at random with a password error.</td></tr><tr><td>Sign-in</td><td>Signing out of other sessions really ends them. Employees can use Forgot password again. The sign-in page asks for an email, unused social sign-in buttons are hidden, and a lost sign-in returns to the sign-in page. The two-step verification page footer no longer overlaps.</td></tr><tr><td>Public dashboard</td><td>A workspace's public dashboard now shows that workspace's own data, not the state's. Turning on the public dashboard in a self-serve workspace now shows the standard indicators; before, it had nothing to show.</td></tr><tr><td>Configurator and onboarding</td><td>All boundary hierarchies are listed. Duplicate boundary codes are caught before saving. Jurisdictions and departments can be revoked. Settings save reliably, and setup progress keeps updating to the end. Older workspaces can use the new workspace screens. Branding finds the workspace in large installations. Sign-up no longer stops on a boundary timing error. Employee templates and screens are corrected.</td></tr><tr><td>Notifications</td><td>Upgrading no longer fails when a workspace already uses the same internal permission numbers.</td></tr><tr><td>Screens (both apps)</td><td>Long dropdown options, inbox cells, complaint numbers and statuses show in full. Text with a colon is no longer cut. Themes apply to the whole page, buttons keep readable labels, and screen text is translated.</td></tr><tr><td>WhatsApp</td><td>Long complaint menus work, and tenants without a complaint template can file.</td></tr><tr><td>Deployment</td><td>An upgrade can no longer wipe an existing database. Remote deployments and fresh-machine setups work again.</td></tr><tr><td>Monitoring</td><td>The status board no longer reports a false failure on hardened servers.</td></tr></tbody></table>

## Changes

v2.20 is not a drop-in upgrade from v2.12: sign-in, web addresses and several services change. Plan a staged upgrade on a test environment first. The [deployment changelog](https://docs.digit.org/complaints-management/release-notes/deployment-changelog.md) has the settings to change and the upgrade steps.

<table><thead><tr><th width="340.171875">What changes</th><th>Who is affected</th><th>What to do</th></tr></thead><tbody><tr><td>Everyone signs in through the new sign-in service; the old login pages are gone.</td><td>All users, custom app versions</td><td>Use the new sign-in. Update any customised login screens.</td></tr><tr><td>App addresses now include the workspace name. Old bookmarks stop working unless a default workspace is set.</td><td>Users with bookmarks, external links</td><td>Update links, or ask operations to set a default workspace.</td></tr><tr><td>Existing staff can sign in only after they are linked to the new sign-in service. Staff whose home is a city tenant cannot be linked and lose sign-in unless they are re-created at the state level.</td><td>All existing employees</td><td>Ask operations to link staff during the upgrade. Plan for city-tenant staff.</td></tr><tr><td>Employees reset passwords by email; reset by SMS is removed.</td><td>Employees without an email address</td><td>Add email addresses to staff records before upgrading.</td></tr><tr><td>Citizens can no longer sign in with Google; they sign in with their phone and a one-time code.</td><td>Citizens who used Google</td><td>Tell citizens about the change.</td></tr><tr><td>The old citizen address (<code>/citizen</code>) no longer works. The citizen app is at <code>/&#x3C;workspace>/digit-ui/citizen</code>.</td><td>Citizens with bookmarks, external links</td><td>Update links.</td></tr><tr><td>Swahili is no longer offered when signing up a new workspace. Existing Kenyan workspaces keep it.</td><td>New Swahili-speaking workspaces</td><td>Plan translations if needed.</td></tr><tr><td>Citizen sign-in is off until it is switched on.</td><td>Citizen-facing workspaces</td><td>Choose the citizen sign-in methods during the upgrade.</td></tr><tr><td>Automatic escalation is off after upgrading, and escalation works differently.</td><td>Workspaces upgraded from v2.12</td><td>Review escalation settings, and ask operations to turn automatic escalation back on. It is one switch for the whole installation, not per workspace.</td></tr><tr><td>Notifications move to per-workspace settings. Existing workspaces send no complaint notifications until they are migrated.</td><td>Workspaces using notifications</td><td>Run the notification migration for each workspace.</td></tr><tr><td>Only administrators can open the Configurator.</td><td>Staff who used it without an admin role</td><td>Grant admin roles where needed.</td></tr><tr><td>Employee import templates use the employee code as the username.</td><td>Admins doing bulk imports</td><td>Use the new templates.</td></tr><tr><td>Analytics events have new names.</td><td>Teams with analytics reports</td><td>Update reports to the new names.</td></tr><tr><td>Several back-end services are replaced, and some systems that called the old ones directly stop working.</td><td>Integrators, operations</td><td>Move integrations to the new sign-in service.</td></tr></tbody></table>

**Rollback.** No full rollback path to v2.12.1 is confirmed yet. Back up all data before upgrading.

### Security

**Security**

* More than 30 findings from a partner security audit are fixed, including both high-severity ones. Six remain open (see below and section H).
* Hundreds of known vulnerabilities in third-party libraries are fixed, including a critical database-driver issue.
* Sign-in is hardened: security tokens stay on the server, sessions end when credentials change, and staff cannot grant themselves admin rights.
* Each workspace's data stays within that workspace in search, look-ups and preferences. The public dashboard now does too; before this release it could show the state's data.
* Servers expose fewer network ports, run a firewall, and send stricter browser security headers.
* Six audit items are still open (section H).

**Reliability**

* An upgrade can no longer wipe an existing database by accident.
* Onboarding retries failed steps on its own.
* Escalation checks are logged one by one, so a failure is easier to find.

**Performance**

No performance measurements were available for this release.

### Known Issues&#x20;

Escalation issues are tracked in detail in [Known issues](https://docs.digit.org/complaints-management/release-notes/known-issues.md).

<table><thead><tr><th width="120.9453125">Area</th><th width="496.8671875">Issue</th><th>Status</th></tr></thead><tbody><tr><td>Escalation</td><td>A Grievance Routing Officer can assign straight to a senior manager and skip the chain.</td><td>Open</td></tr><tr><td>Escalation</td><td>Complaints rejected and then reopened do not escalate automatically.</td><td>Open</td></tr><tr><td>Access</td><td>Limiting the Configurator to administrators covers the screens only; some staff data can still be read by non-admin roles through the system's interfaces.</td><td>Open</td></tr><tr><td>Sign-in</td><td>Workspace branding can disappear when a timed-out sign-in restarts. The new email sign-in wording is English only.</td><td>Open</td></tr><tr><td>Sign-in</td><td>The setup email for non-admin staff opens the Configurator instead of the employee app.</td><td>Open</td></tr><tr><td>Sign-in</td><td>Signing in as staff right after a Configurator session can fail with "already authenticated as a different user".</td><td>Open</td></tr><tr><td>Sign-in</td><td>A citizen's emailed email-change link returns to the default workspace instead of the citizen's own. Staff links were fixed in #2731.</td><td>Open</td></tr><tr><td>Sign-in</td><td>Staff who also use the citizen app with the same phone number count as two people; joining them is optional and off by default.</td><td>Open</td></tr><tr><td>Onboarding</td><td>Setup can show a "usually temporary" boundary error and then fail on Try again, although the setup succeeded.</td><td>Open</td></tr><tr><td>Notifications</td><td>One provider per channel per workspace, with no automatic failover.</td><td>By design in this release</td></tr><tr><td>Notifications</td><td>WhatsApp messages need each workspace's own approved templates.</td><td>Register templates with the provider</td></tr><tr><td>Notifications</td><td>Twilio messages show "Sent" even after delivery. The new notification screens are English only.</td><td>Open</td></tr><tr><td>Notifications</td><td>Citizen sign-in by phone does not use the new notification service yet.</td><td>Needs a separate SMS sender</td></tr><tr><td>Monitoring</td><td>Sign-in service metrics may not be collected, depending on the deployment settings.</td><td>Open</td></tr><tr><td>Security</td><td>Six audit items remain open, including a seeded default password and anonymous file downloads.</td><td>Open</td></tr></tbody></table>

### Impact and action required

<table><thead><tr><th width="137.58984375">Audience</th><th width="401.48046875">What changes for them</th><th>Action</th></tr></thead><tbody><tr><td>Citizens and employees</td><td>New sign-in, workspace-specific links, a three-step complaint form with voice input, a new employee console. Employees reset passwords by email. Citizens sign in with phone and code.</td><td>Update bookmarks. Make sure every employee has an email address.</td></tr><tr><td>Government administrators</td><td>Self-serve onboarding, the escalation policy editor, notification settings, branding, public dashboard controls, app links. Automatic escalation is off after upgrading.</td><td>Review escalation settings. Set up notification providers and messages. Use the new employee templates.</td></tr><tr><td>Partners</td><td>Many governments on one installation, each set up without eGov support, with an optional 30-day trial.</td><td>Decide on trial use and analytics accounts per deployment.</td></tr><tr><td>Developers and integrators</td><td>Sign-in goes through the new sign-in service; old user endpoints are closed. New onboarding and notification services.</td><td>Follow the <a href="https://docs.digit.org/complaints-management/release-notes/deployment-changelog.md">deployment changelog</a>. Update custom login code.</td></tr><tr><td>QA teams</td><td>Wide changes to screens and workflows.</td><td>Regression-test sign-in for every role, onboarding end to end, the complaint lifecycle including escalation and reopen, notifications per channel, French and Portuguese, phone layouts, and WhatsApp if used.</td></tr><tr><td>Operations teams</td><td>New and retired services, new settings and secrets, data migrations, linking existing staff to the new sign-in.</td><td>Follow the upgrade steps in the <a href="https://docs.digit.org/complaints-management/release-notes/deployment-changelog.md">deployment changelog</a>. Back up all databases first.</td></tr></tbody></table>

## Related Docs

<table><thead><tr><th width="285.6640625">Document</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://docs.digit.org/complaints-management/community/roadmap">Complaint Management roadmap</a></td><td>Product roadmap</td></tr><tr><td><a href="https://docs.digit.org/complaints-management/release-notes/deployment-changelog.md">Deployment Changelog</a></td><td>Configuration &#x26; infrastructure changelog (city data, service settings, DevOps)</td></tr><tr><td><a href="https://docs.digit.org/complaints-management/release-notes/migration-guide.md">Migration Guide</a></td><td>Operator upgrade procedure v2.11 → v2.12</td></tr><tr><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications.md">Notifications </a></td><td>Notifications setup guide (SMS, WhatsApp, email)</td></tr><tr><td><a href="https://docs.digit.org/complaints-management/access/account-creation-and-onboarding-guide.md">Configurator onboarding guide</a></td><td>setup and configure the complaint management system</td></tr><tr><td><a href="https://docs.digit.org/complaints-management/access/management-console-guide.md">Configurator management guide</a></td><td>manage the complaint management system</td></tr></tbody></table>


---

# 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/release-notes.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.
