Difference between revisions of "Registering Grievance"

From JUNO Wiki
Jump to: navigation, search
(Step by step)
(Functionality)
Line 15: Line 15:
 
*
 
*
 
== <b>Functionality</b> ==
 
== <b>Functionality</b> ==
1) <b>Grievance Report</b>
+
1) <b>Raise Grievance</b>
  
*  
+
* Faculty from their login can raise grievance.
 +
* Complaint priority can be given between Low to High.
 +
* From an specific admin login(Library Head, Academic Head, etc.) complaint can be forwarded to respective member or coordinator.
 +
* Complaint proof can be uploaded images, document, etc.
  
 
2) <b>Complaint History</b>
 
2) <b>Complaint History</b>
  
* Grievances under a particular type can be defined.
+
* Complaint history can be traced.
*  
+
* Past complaint with their status can be maintained.
 
 
  
 
== '''Step by step''' ==
 
== '''Step by step''' ==

Revision as of 07:50, 7 October 2019

Registering Grievance

Grievance configuration allows the prior configuration steps that are required to enable grievance module functioning. After configuration completion Employee can raise grievance and the same can be addressed by authority allocated by committee for same.

Roles

Employee Login, Faculty Login

Path

Faculty >> Requisitions >> Grievance >> Employee Grievance

OR

Staff >> Feedback Grievance >> Raise Observations

Inputs Needed

Functionality

1) Raise Grievance

  • Faculty from their login can raise grievance.
  • Complaint priority can be given between Low to High.
  • From an specific admin login(Library Head, Academic Head, etc.) complaint can be forwarded to respective member or coordinator.
  • Complaint proof can be uploaded images, document, etc.

2) Complaint History

  • Complaint history can be traced.
  • Past complaint with their status can be maintained.

Step by step

Follow Below mentioned steps
  • Raise Grievance from Faculty login
GRRE1.png


  • Complaint History
GRRE2.png


  • Raise Grievance from Staff login
GRRE3.png