> 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/account-creation-and-onboarding-guide/employees.md).

# Employees

## Overview

Employees are the people who will use the system to handle and resolve complaints. Each person gets their own sign-in, a department, a designation, the roles that determine what they can do in CMS, and the areas they cover.

{% hint style="info" %}
**Note:** An admin who onboards and sets up an account is already listed as the first employee, marked "(you)". You do not count towards finishing this step, so add at least one other person.

You need at least one department, one designation and your geography in place before you can add employees.
{% endhint %}

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2Fy0h0n1iTIOBwbwT2YdBD%2Funknown.png?alt=media&amp;token=17f0995a-9442-4135-b075-eb09f3b1c686" alt="" height="391" width="624"></div>

## Steps

### Step 1. Add an employee

1. Select Create manually (or Add employee).
2. Fill in the boxes described below.
3. Select Add. The person receives an invitation email straight away.

<table><thead><tr><th width="194.88671875">Field</th><th>Notes</th></tr></thead><tbody><tr><td>Employee code</td><td><p>Suggested for you. Example: EMP_0002. You can also edit this and use your own employee numbers. </p><p>It cannot be changed later. </p></td></tr><tr><td>Full name</td><td>Employee’s full name.</td></tr><tr><td>Mobile number</td><td>Without the country code. For Kenya: 9 digits starting with 7 or 1. Each number can be used for only one employee.</td></tr><tr><td>Email</td><td>Required. This is where their invitation goes.</td></tr><tr><td>Departments</td><td>Tick one or more. The first one you tick is their main department.</td></tr><tr><td>Designation</td><td>Their job title.</td></tr><tr><td>System roles</td><td>What they can do. Employee is ticked already. See the table below.</td></tr><tr><td>Jurisdictions</td><td>The areas they cover. See Jurisdiction26.</td></tr></tbody></table>

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2F0ZRDRxM6fH4HSv2k0LsF%2Funknown.png?alt=media&amp;token=a6a853b5-09f7-45f7-b085-6d913c0b0df5" alt="" height="391" width="624"></div>

### Step 2. Choose roles

Pick the roles that match each person's job. Most people need the Employee plus one Complaint role.

<table><thead><tr><th width="284.96875">Role shown on screen</th><th>Give it to people who…</th></tr></thead><tbody><tr><td>Employee</td><td>Need to sign in. Everyone has this.</td></tr><tr><td>Complaint Assessor (GRO)</td><td>Receive new complaints  and assign them to an employee from the relevant department.<br>This role is department-agnostic.</td></tr><tr><td>Department GRO (DGRO)</td><td>Assess complaints at department level. </td></tr><tr><td>Complaint Resolver (PGR_LME)</td><td>Field employee who fixes the problem on the ground.</td></tr><tr><td>Citizen Facilitation Counter (CFC)</td><td>Log complaints on behalf of citizens at a help desk.</td></tr><tr><td>Complainant (CSR)</td><td>Raise complaints. This is added to everyone automatically.<br>This role is mainly used for any employee who may choose to file a complaint on a citizen’s behalf.</td></tr><tr><td>CMS Viewer</td><td>This role receives View-only access to complaints.</td></tr></tbody></table>

{% hint style="info" %}
**Important:** Every department that receives complaints needs at least one Complaint Assessor (GRO) whose main department is that department. Without one, you cannot finish the last step.

A Department GRO (DGRO) does not count for this.
{% endhint %}

#### How employees sign in

* New to the system: they receive an email with a link to set their password. The link expires after 15 minutes, so ask them to open it promptly.
* Already have an account with this email: they see your invitation the next time they sign in and choose to accept it. The invitation lasts 14 days.

Each person's row shows where they are:

<table><thead><tr><th width="152.69921875">Label</th><th width="374.10546875">Meaning</th><th>What you can do</th></tr></thead><tbody><tr><td>Active</td><td>They can sign in.</td><td>Resend email</td></tr><tr><td>Invited</td><td>Waiting for them to accept. Shows the expiry date.</td><td>Resend email</td></tr><tr><td>Invite expired</td><td>They did not accept in time.</td><td>Invite again</td></tr><tr><td>No access</td><td>They do not currently have access.</td><td>Invite again</td></tr><tr><td>Not invited</td><td>No invitation has been sent yet.</td><td>Send invite</td></tr></tbody></table>

{% hint style="info" %}
**Tip:** Password link expired? Select Resend email on their row. You can resend once a minute.
{% endhint %}

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2FXcbZj1MJGnbQbzpIGLK9%2Funknown.png?alt=media&amp;token=f6975344-3518-47ad-b149-75704b2903f6" alt="" height="391" width="624"></div>

### Step 3. Add many employees at once (bulk upload)

1. Select Bulk upload, then get the template and download it.
2. Fill in one row per person on the Employee sheet. Delete the two example rows.
3. Upload the file, check the results, and fix any rows marked Error.
4. Select Create Employees and confirm.
5. When it finishes, you can select Download invitations CSV for a list of everyone invited.

<table><thead><tr><th width="156.453125">Data Field</th><th width="458.375">Note</th><th>Required?</th></tr></thead><tbody><tr><td>employeeCode</td><td>A code used to uniquely identify an employee, such as “EMP_002”. If your organisation has employee ID numbers, you may use those here.<br>Leave blank to get one automatically.</td><td>Yes</td></tr><tr><td>name</td><td>Full name of the employee.</td><td>Yes</td></tr><tr><td>mobileNumber</td><td>Without the country code.</td><td>Yes</td></tr><tr><td>emailId</td><td>Email address. Needed for the invitation.</td><td>Yes</td></tr><tr><td>gender</td><td>For example FEMALE or MALE.</td><td>No</td></tr><tr><td>dob</td><td><p>Date of birth in YYYY-MM-DD format, for example, 1990-04-21. </p><p>Must be at least 18 years of age.</p></td><td>No</td></tr><tr><td>department</td><td>Department code(s). The first is their main department. Separate several with commas.<br>These codes can be gathered from the previous onboarding steps.</td><td>Yes</td></tr><tr><td>designation</td><td>Designation code.<br>These codes can be gathered from the previous onboarding steps.</td><td>Yes</td></tr><tr><td>roles</td><td>Role codes separated by commas, for example EMPLOYEE,GRO. Uses EMPLOYEE if blank.</td><td>No</td></tr><tr><td>jurisdictions</td><td>Area codes separated by commas.</td><td>Strongly advised</td></tr><tr><td>dateOfAppointment</td><td>The date they started.</td><td><p>No</p><p><br></p></td></tr></tbody></table>

<div align="left"><img src="https://2002286464-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK894BCuKVRy7QDBs06em%2Fuploads%2Fkwd4ZGLGgjAgITB8yDrv%2Funknown.png?alt=media&amp;token=21d23737-513f-4293-a805-5c1e232b2020" alt="" height="391" width="624"></div>

### Step 4. Edit or remove an employee

* Edit: select Edit on their row. Changes apply the next time they sign in. If you change their email, a confirmation link goes to the new address.
* Remove: select Remove. They can no longer sign in or handle complaints. You cannot remove yourself.

### If something goes wrong

<table><thead><tr><th width="352.30078125">What you see</th><th>What to do</th></tr></thead><tbody><tr><td>That number doesn't match this workspace's mobile format.</td><td>Check the number of digits and the first digit.</td></tr><tr><td>Mobile "…" already exists</td><td>Each mobile number can belong to only one employee.</td></tr><tr><td>Another employee already has this code.</td><td>Use the suggested code.</td></tr><tr><td>… added, but not invited</td><td>The person was saved. Select Send invite on their row.</td></tr><tr><td>An email went to them less than a minute ago.</td><td>Wait one minute and resend.</td></tr><tr><td>This email already belongs to a different employee in this workspace.</td><td>Use a different email address.</td></tr><tr><td>Your sign-in has ended, so nobody was added.</td><td>Sign out, sign in again, and add them again.</td></tr><tr><td>Set up your geography first.</td><td>Finish the Geography step.</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/access/account-creation-and-onboarding-guide/employees.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.
