Introduction
This section covers the features that come under the Administrator purview, which is mostly done once when the system is made up or when there is some change in the setups.
Prerequisites
Log in to the system with a user who has "Super User" role access.
Domain names configured for each city. If its a statewide implementation, then have one main domain for the state and one subdomain each per city.
Functionality
City Set up
Each city will have a dedicated URL based on the subdomain configured. All city specific details can be captured here including the logo. All information can be updated through the screen provided from the City Set up. Each instance will ideally have one data for city master.
Role
Multiple roles can be created in the system based on the access control required. Each role is for a specific purpose.
User Management
Users in the system belong to basically three categories- Citizens, Employees and Business users. Each user can be assigned to a list of roles and authorization will be done in the system based on this mapping. Any role can be added or removed from a user using this feature at any point in time. The menu tree list in the application will be loaded based on this mapping.
Boundary set up
Each state or city will have its own specific boundary definitions. The system allows configuring multiple hierarchies, which in turn can define a boundary type and then the actual boundary master. For instance, in a state, the boundary limits will be different for administration and elections. The system enables us to configure a different set of hierarchy for each of these. Also, there is a provision to link different hierarchies which will enable the system to get the data across hierarchies.
Authorization setting
Department
Configurations and Setup
For the sever to come up for a specific city, an entry needs to be made in the eg_city table with proper domain url. This is the very first thing that needs to be done as part of the system set up.