> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/~/changes/xKUM0sBXFkyR8F24yAMq/social-registry/functionality/administration.md). # Administration / User Management ## Introduction 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 steps are involved: 1. **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. 2. **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. 3. **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. 4. **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 ## Roles Each role in the Social Registry system plays a critical part in ensuring the accurate collection, management, and security of data, ultimately contributing to the effective operation of the system
Role Responsibilities
Administrator
  • The Administrator role in the Social Registry system is responsible for overall system management and configuration.
  • Administrators have permissions to manage user accounts, configure system settings, and oversee the general operation of the system.
  • 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.
Crypto Administrator
  • The Crypto Administrator plays a crucial role within the security module of the system.
  • This role is responsible for managing and securing cryptographic keys, overseeing encryption practices, and ensuring data integrity and protection against unauthorized access.
  • The Crypto Administrator is vital in maintaining the confidentiality, availability, and integrity of sensitive information.
Registrar
  • A Registrar is a role within the Social Registry system responsible for maintaining Registry records.
  • Registrars have specific permissions related to adding, editing, and managing registrant information within the system, while also having restrictions to ensure data integrity and security.
Enumerator
  • Enumerators are individuals responsible for collecting demographic data from individuals and households to populate data in the registry.
  • Enumerators are typically field workers who visit households, communities, or places to gather the necessary information.
Service Provider / Operator
  • Service providers refer to institutions or organizations responsible for collecting data on individuals and households
The figure below shows below some of the roles or access levels that can be assigned to users
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openg2p.org/~/changes/xKUM0sBXFkyR8F24yAMq/social-registry/functionality/administration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.