Role Based Access Control
In the Social Registry, user management is typically handled through an administrative interface that allows administrators to create, modify, and deactivate user accounts. The specific process may vary depending on the system's design and configuration, but generally, the following process are involved:
User Creation: Administrators can create new user accounts by entering basic information such as username, password, and email address. They may also assign roles and permissions to the new user.
Role Assignment: Users are assigned roles based on their responsibilities within the system. Roles determine the permissions and access rights that users have within the system.
User Activation and Deactivation: Administrators can activate or deactivate user accounts as needed. Deactivating an account prevents the user from accessing the system, while activating an account restores access.
Audit Logs: The system may keep audit logs of user activity, recording actions such as login attempts, changes to user accounts, and access to sensitive data. Audit logs help administrators monitor user activity and identify potential security issues
User Roles
The following lists the different users in the Social Registry module along with their roles and responsibilities.
User Role | Role and Responsibility |
---|---|
Super Administrator | Role The Super Administrator has the highest level of administrative access. Responsibility Total command of the system such as
|
System Administrator | Role The System Administrator manages the technical and operational aspects of the system. Responsibility
|
Crypto Administrator | Role The Crypto Administrator plays a crucial role in the system's security module. Responsibility
|
Registrar | Role The Registrar manages the registration process of individuals in the Social Registry module. Responsibility
|
Data Administrator | Role The Data Administrator manages the data in the Social Registry module. Responsibility
|
Data Validator | Role The Data Validator ensures the accuracy and validity of the data collected. Responsibility
|
Data Collector (Registration portal user) | Role The Data Collector collects data through the registration portal. Responsibility
|
Data Enumerator (Same as Data collector but offline) | Role The Data Enumerator collects data offline, often in the field. Responsibility
|
Data Collection Supervisor | Role The Data Collection Supervisor oversees and manages the Registration Portal's data collection team to ensure accurate and effective data gathering. Responsibility
|
Custom configuration for user roles
User Role | Add | Edit | Approve | Edit count before lock | Request for edit | Edit request approver | Approve edit requests | Request for correction | Correction requested to |
---|---|---|---|---|---|---|---|---|---|
Super Administrator | Yes | Yes | Yes | -1 | NA | NA | Yes | No | NA |
System Administrator | No | No | No | NA | NA | NA | No | No | NA |
Crypto Administrator | No | No | No | NA | NA | NA | No | No | NA |
Registrar | Yes | Yes | Yes | -1 | NA | NA | Yes | No | NA |
Data Administrator | Yes | Yes | No | 2 | Yes | Super/System Administrator | Yes | No | NA |
Data Validator | No | No | Yes | NA | No | NA | No | Yes | Data Collector |
Data Enumerator | Yes | No | No | 1 | Yes | Data Administrator /Registrar | No | No | NA |
Data Collector | Yes | Yes | No | 1 | Yes | Data Administrator /Registrar | No | No | NA |
Data Collection Supervisor | Yes | Yes | No | 1 | Yes | Data Administrator /Registrar | No | Yes | Data Collector |
Notes:
Edit count before lock | Description |
---|---|
-1 | The user is free to edit the data without any limitations. |
1 | The user is allowed to make changes to the data only once. |
2 | The user is allowed to make changes to the data two times. |
Last updated