> 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/sandbox/specifications/user-manual/complaints-user-manual/employee-user.md).

# Employee User

Refer to the [Logging Into Sandbox](/sandbox/specifications/user-manual/logging-into-sandbox.md) page to log in as an employee user. The [Role-Action Mapping](#role-action-mapping) table below provides the role-specific details configured for employee users.

Employee users can -

1. [File complaints](/sandbox/specifications/user-manual/complaints-user-manual/employee-user/file-complaints.md)
2. [View complaints](/sandbox/specifications/user-manual/complaints-user-manual/employee-user/view-complaints.md)
3. [Assign/reject complaints](/sandbox/specifications/user-manual/complaints-user-manual/employee-user/assign-reject-complaint.md)
4. [Resolve complaints](/sandbox/specifications/user-manual/complaints-user-manual/employee-user/resolve-complaint.md)
5. [Configure complaint masters](/sandbox/specifications/user-manual/complaints-user-manual/employee-user/configure-complaint-masters.md)

## Role-Action Mapping

The list of roles and corresponding actions each role can perform is listed below:

<table><thead><tr><th width="214">Role</th><th>Description</th></tr></thead><tbody><tr><td>Superuser</td><td>All actions associated with Sandbox &#x26; its products</td></tr><tr><td>Admin</td><td>Employee Management + All Complaints actions (including viewing dashboards)</td></tr><tr><td>Employee</td><td>View Inbox</td></tr><tr><td>Complaints-Admin</td><td>All Complaints actions (including viewing dashboards)</td></tr><tr><td>Assigner</td><td>File Complaint, Assign Complaint, Reject Complaint, Reassign Complaint</td></tr><tr><td>Resolver</td><td>Resolve Complaint</td></tr></tbody></table>

## Complaint Status

As part of the Complaints product workflow, each complaint can have multiple statuses throughout its lifecycle. A brief overview of statuses is given below:

<table><thead><tr><th width="272">Status</th><th>Description</th></tr></thead><tbody><tr><td>Pending For Assignment</td><td>A complaint has been filed and needs to be assigned to an employee for resolution.</td></tr><tr><td>Pending at LME</td><td>The complaint has been assigned to an employee for resolution. However, the employee has not yet resolved the complaint.</td></tr><tr><td>Resolved</td><td>The complaint has been marked as resolved by the employee. However, the citizen has not yet rated the resolution process.</td></tr><tr><td>Closed After Resolution</td><td>The citizen who filed the complaint has rated the resolution process. The complaint is now closed.</td></tr><tr><td>Pending for Reassignment</td><td>The complaint has to be reassigned to another employee.</td></tr><tr><td>Rejected</td><td>The complaint is deemed invalid and is currently not to be processed further.</td></tr><tr><td>Closed After Rejection</td><td>An end state for the complaint - No further action can be taken on it.</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 dynamically by asking a question.

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

```
GET https://docs.digit.org/sandbox/specifications/user-manual/complaints-user-manual/employee-user.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.