- List of Issue Categories it can handle
- List of locality it can serve
- Make and Delete Announcements
- Define and assign different levels of administrative roles (L1,L2,L3)
- Revoking access and reassigning roles
- List of Issues which are open and closed and which level of admistration is working on it
-
New Issue
- Select Department
- Select Issue Category and Description
- Personal details
-
Dashboard
- Current Pending Issues
- Close solved issues or reopen them
- Announcements
* Data Visualisation
* Administrative role panel
> List of Pending Issues
* Accept
* Escalate to higher admistrative role( From L1 to L2 or further )
* Mark as spam
* KYC
* Handling Spam
Do not allow modifications to an issue after it is finalised, maybe add a way to create a draft before making it permanent.
For further ideas,
KYC would be redundant as the Data will already be present in the Customer Portal. Make it so that the Corporations won't have access to it straightaway, just only the relevant details needed for the issue. Most issues would be kept personal unless the company asks and then send a notification to the person for his approval... The central databases can be used to coordinate this or simply make some other relational db which will not be accessed by neither parties and would only be used by the application admin.
Spam handling would be a bit difficult as we need to somehow classify the issues as spam or not spam. Maybe a guideline which can be imposed by the Corporations as to what would be considered spam can be implemented but then thats a human factor.