> ## Documentation Index > Fetch the complete documentation index at: https://docs.hitaji360.com/llms.txt > Use this file to discover all available pages before exploring further. # Grievances > A grievance is a formal complaint raised by an employee — about a colleague, a manager, working conditions, or anything else they want HR to look into. A grievance is a formal complaint raised by an employee — about a colleague, a manager, working conditions, or anything else they want HR to look into. In Hitaji 360, employees raise grievances themselves through the self-service portal (see [My grievances](/hr/user/self-service/my-grievances)), and HR works them from this side: triaging, investigating, and resolving each one with a documented outcome. This page covers the **HR view** — the list of grievances raised across the business, how you move one through investigation, and how you close it. **You'll find this at:** `/hr/grievances` (list) and `/hr/grievances/:id` (detail). > 📷 *Screenshot: the Grievances list showing the reference (HR-GRV-…), subject, raised-by, and status columns — to be added.* *** ## Before you start * **Which business am I in?** A grievance belongs to one business and is invisible to HR working in another. The employee's grievance is automatically stamped with the business of their own employment contract, so it lands in the right HR queue. * **HR doesn't raise grievances here.** The **Raise Grievance** button on the HR list is intentionally disabled — grievances are raised by the employee through the self-service portal or from the employee's profile, never planted by HR on someone's behalf. *** ## The grievance list Each grievance shows its reference (e.g. `HR-GRV-2026.06.0001`), subject, who raised it, who it is against (if anyone), the date, its status, and its type. Click a row to open it. *** ## The grievance lifecycle (statuses) | Status | Meaning | What you can do | | ----------------------- | --------------------------------- | --------------------------------------------- | | **Open** | Newly raised; not yet picked up. | Mark Under Investigation, Resolve, or Cancel. | | **Under Investigation** | HR is looking into it. | Resolve, Mark Invalid, or Cancel. | | **Resolved** | Closed with a documented outcome. | View only. | | **Invalid** | Found to be unfounded. | View only. | | **Cancelled** | Withdrawn or cancelled. | View only. | A few rules the system enforces: * You can move **Open → Under Investigation / Resolved / Cancelled**, but **not Open → Invalid** — marking a grievance Invalid is only offered once it is Under Investigation (so there is a record of investigation behind that verdict). * **Resolving** requires you to fill in the cause, the resolution detail, and a resolution date (see below). * **Resolved**, **Invalid** and **Cancelled** are terminal — no further changes. *** ## Working a grievance On the detail page you'll see the subject, full description, who raised it, who it is against (optional), the date, and the grievance type. The available actions depend on the current status. ### Mark Under Investigation From **Open**, choose **Mark Under Investigation** to signal HR has picked it up. No extra detail is required. ### Resolve From **Open** or **Under Investigation**, choose **Resolve** and complete the inline form: | Field | Required | Notes | | ---------------------- | -------- | ------------------------------------------------ | | **Cause of grievance** | Yes | The root cause established during investigation. | | **Resolution detail** | Yes | How the grievance was resolved. | | **Resolution date** | Yes | When it was resolved. | Resolving stamps who resolved it and moves the grievance to **Resolved**. ### Mark Invalid From **Under Investigation**, choose **Mark Invalid** (a destructive action) when the complaint is unfounded. It requires a **cause** to document the basis for that decision. ### Cancel A grievance can be cancelled from Open or Under Investigation. > **Assignment.** The grievance record can carry a *person responsible* for handling it. Use this to track who owns the investigation. *** ## How employees raise grievances Employees raise grievances through the self-service portal at `/my-hr/grievances` (or from the employee profile). They provide a **subject** and a **description**, and optionally a grievance **type** and the person it is **against**. The system forces the grievance to be filed under the employee's own identity and their own business — an employee cannot file on someone else's behalf or push a grievance into another business's queue. > **Known fix — no blank grievances.** The raise-grievance form requires a non-blank subject and description. Both fields are trimmed and then validated as non-empty, so a whitespace-only entry like `" "` is rejected rather than creating an empty grievance. For the full employee-side experience, see [My grievances](/hr/user/self-service/my-grievances). *** ## Grievance types Grievances can be classified by **type** (e.g. Harassment, Pay, Working Conditions). Types are simple named, active/inactive labels managed under HR; an employee can pick one when raising a grievance, and HR can filter by it. *** ## Permissions | Action | Permission | | -------------------------------------------------------------------------------- | ---------- | | View grievances and types | `hr:read` | | Update a grievance (investigate, resolve, invalidate, cancel), create/edit types | `hr:write` | > Employees raising their own grievances through self-service do so under a self-only guard, not these HR slugs. *** ## Related * [My grievances](/hr/user/self-service/my-grievances) — the employee-side "raise a grievance" experience * [Exit interviews](/hr/user/lifecycle/exit-interviews) — the other lifecycle record HR manages * [The employee profile & its tabs](/hr/user/employees/employee-profile) — the per-employee Grievances tab