From 07659f889f73b4c78a1e8a10863eaa3fcda46c3e Mon Sep 17 00:00:00 2001 From: Puneet Joshi Date: Wed, 16 Oct 2024 02:21:39 +0000 Subject: [PATCH] GITBOOK-1125: No subject --- SUMMARY.md | 57 ++++++++----------- ...figure-inji-to-download-beneficiary-vcs.md | 4 +- social-registry/README.md | 2 - .../features/administration/README.md | 15 +++-- .../features/administration/user-roles.md | 27 --------- social-registry/features/attestation.md | 6 -- .../features/{logging => }/audit-log.md | 15 ++++- social-registry/features/consent.md | 2 - .../features/deduplication/README.md | 4 +- .../features/domain-specific-registries.md | 2 - social-registry/features/enumerator/README.md | 3 +- .../features/enumerator/enumerator-id.md | 2 +- social-registry/features/id-creation.md | 12 ---- .../features/id-integration/README.md | 2 + .../fayda-id-integration.md | 0 .../id-authentication/README.md | 4 +- .../id-authentication/user-guides/README.md | 0 ...net-auth-provider-for-id-authentication.md | 18 +++--- .../user-guides/esignet-client-creation.md | 0 .../user-guides/id-authentication-process.md | 6 +- .../id-integration}/tokenisation.md | 4 +- .../features/individuals-and-groups/README.md | 18 ++---- social-registry/features/interoperability.md | 5 +- social-registry/features/lock-and-unlock.md | 20 +++---- social-registry/features/logging/README.md | 2 - .../features/logging/audit-log-advanced.md | 14 ----- .../features/monitoring-and-reporting.md | 3 + .../monitoring-and-reporting/README.md | 2 - .../monitoring-and-reporting/system-logs.md | 3 - social-registry/features/notifications.md | 17 ------ .../features/record-revision-history.md | 2 +- social-registry/features/score-computation.md | 6 +- social-registry/features/search-opensearch.md | 6 -- social-registry/features/search.md | 2 - social-registry/features/single-sign-on.md | 8 --- ...d => spar-integration-for-account-info.md} | 5 +- .../features/unique-reference-id.md | 4 -- .../verifiable-credentials-issuance.md | 6 +- 38 files changed, 95 insertions(+), 213 deletions(-) delete mode 100644 social-registry/features/administration/user-roles.md delete mode 100644 social-registry/features/attestation.md rename social-registry/features/{logging => }/audit-log.md (70%) delete mode 100644 social-registry/features/consent.md delete mode 100644 social-registry/features/domain-specific-registries.md delete mode 100644 social-registry/features/id-creation.md create mode 100644 social-registry/features/id-integration/README.md rename social-registry/features/{ => id-integration}/fayda-id-integration.md (100%) rename social-registry/features/{ => id-integration}/id-authentication/README.md (83%) rename social-registry/features/{ => id-integration}/id-authentication/user-guides/README.md (100%) rename {pbms/functionality/id-verification => social-registry/features/id-integration/id-authentication}/user-guides/configure-esignet-auth-provider-for-id-authentication.md (77%) rename social-registry/features/{ => id-integration}/id-authentication/user-guides/esignet-client-creation.md (100%) rename social-registry/features/{ => id-integration}/id-authentication/user-guides/id-authentication-process.md (75%) rename social-registry/{development/upcoming-features => features/id-integration}/tokenisation.md (85%) delete mode 100644 social-registry/features/logging/README.md delete mode 100644 social-registry/features/logging/audit-log-advanced.md create mode 100644 social-registry/features/monitoring-and-reporting.md delete mode 100644 social-registry/features/monitoring-and-reporting/README.md delete mode 100644 social-registry/features/monitoring-and-reporting/system-logs.md delete mode 100644 social-registry/features/notifications.md delete mode 100644 social-registry/features/search-opensearch.md delete mode 100644 social-registry/features/search.md delete mode 100644 social-registry/features/single-sign-on.md rename social-registry/features/{spar-update-for-offline-enumerations.md => spar-integration-for-account-info.md} (97%) diff --git a/SUMMARY.md b/SUMMARY.md index ce5ba54f..f5e438b1 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -220,8 +220,17 @@ * [Enumerator](social-registry/features/enumerator/README.md) * [Enumerator ID](social-registry/features/enumerator/enumerator-id.md) * [Dynamic Updates](social-registry/features/registry-update-mechanisms.md) - * [ID Creation](social-registry/features/id-creation.md) * [Document Upload](social-registry/features/document-upload.md) + * [ODK Importer](social-registry/features/odk-importer/README.md) + * [📔 User Guide](social-registry/features/odk-importer/user-guide/README.md) + * [📔 Configure and Import ODK Form](social-registry/features/odk-importer/user-guide/configure-and-import-odk-form.md) + * [📔 Import Specific ODK Forms using ODK Instance ID](social-registry/features/odk-importer/user-guide/import-specific-odk-forms-using-odk-instance-id.md) + * [Registration Portal](social-registry/features/registration-portal/README.md) + * [📔 User Guides](social-registry/features/registration-portal/user-guides/README.md) + * [📔 Create a New Household](social-registry/features/registration-portal/user-guides/create-a-new-household.md) + * [📔 Create a New Individual in Registration Portal](social-registry/features/registration-portal/user-guides/create-a-new-individual-in-registration-portal.md) + * [📔 Create a New Portal User](social-registry/features/registration-portal/user-guides/create-a-new-portal-user.md) + * [📔 Configure Portal User to Limit Accessing Location](social-registry/features/registration-portal/user-guides/configure-portal-user-to-limit-accessing-location.md) * [Configurations](social-registry/features/configurations/README.md) * [📔 User Guide](social-registry/features/configurations/user-guide/README.md) * [📔 Configure ID Types](social-registry/features/configurations/user-guide/configure-id-types.md) @@ -230,15 +239,7 @@ * [📔 Configure Relationships](social-registry/features/configurations/user-guide/configure-relationships.md) * [📔 Configure Group Types](social-registry/features/configurations/user-guide/configure-group-types.md) * [📔 Configure Group Membership Kind](social-registry/features/configurations/user-guide/configure-group-membership-kind.md) - * [Registration Portal](social-registry/features/registration-portal/README.md) - * [📔 User Guides](social-registry/features/registration-portal/user-guides/README.md) - * [📔 Create a New Household](social-registry/features/registration-portal/user-guides/create-a-new-household.md) - * [📔 Create a New Individual in Registration Portal](social-registry/features/registration-portal/user-guides/create-a-new-individual-in-registration-portal.md) - * [📔 Create a New Portal User](social-registry/features/registration-portal/user-guides/create-a-new-portal-user.md) - * [📔 Configure Portal User to Limit Accessing Location](social-registry/features/registration-portal/user-guides/configure-portal-user-to-limit-accessing-location.md) - * [Notifications](social-registry/features/notifications.md) - * [Administration / User Management](social-registry/features/administration/README.md) - * [User Roles](social-registry/features/administration/user-roles.md) + * [User Management](social-registry/features/administration/README.md) * [📔 User Guide](social-registry/features/administration/user-guide/README.md) * [📔 Create User](social-registry/functionality/administration/user-guide/create-user-and-assign-role.md) * [📔 Assign a Role to a User](social-registry/features/administration/user-guide/assign-a-role-to-a-user.md) @@ -251,36 +252,24 @@ * [Search APIs](social-registry/features/api/search-apis.md) * [Individual APIs](social-registry/features/api/individual-apis.md) * [Group APIs](social-registry/features/api/group-apis.md) - * [Search](social-registry/features/search.md) * [Privacy and Security](social-registry/features/privacy-and-security.md) * [Interoperability](social-registry/features/interoperability.md) - * [Monitoring and Reporting](social-registry/features/monitoring-and-reporting/README.md) - * [System Logs](social-registry/features/monitoring-and-reporting/system-logs.md) - * [Fayda ID Integration](social-registry/features/fayda-id-integration.md) + * [Monitoring and Reporting](social-registry/features/monitoring-and-reporting.md) + * [ID Integration](social-registry/features/id-integration/README.md) + * [ID Validation and Tokenisation](social-registry/features/id-integration/tokenisation.md) + * [ID Authentication](social-registry/features/id-integration/id-authentication/README.md) + * [📔 User Guides](social-registry/features/id-integration/id-authentication/user-guides/README.md) + * [📔 Configure eSignet Auth Provider for ID Authentication](social-registry/features/id-integration/id-authentication/user-guides/configure-esignet-auth-provider-for-id-authentication.md) + * [📔 ID Authentication Process](social-registry/features/id-integration/id-authentication/user-guides/id-authentication-process.md) + * [📔 eSignet Client Creation](social-registry/features/id-integration/id-authentication/user-guides/esignet-client-creation.md) + * [Fayda ID Integration](social-registry/features/id-integration/fayda-id-integration.md) * [Verifiable Credentials Issuance](social-registry/features/verifiable-credentials-issuance.md) - * [Benefit Targeting Methods](social-registry/features/score-computation.md) + * [Computed fields](social-registry/features/score-computation.md) * [Record Revision History](social-registry/features/record-revision-history.md) - * [Domain Specific Registries](social-registry/features/domain-specific-registries.md) - * [Single Sign-On](social-registry/features/single-sign-on.md) - * [ID Validation and Tokenisation](social-registry/development/upcoming-features/tokenisation.md) - * [Search - OpenSearch](social-registry/features/search-opensearch.md) - * [Attestation](social-registry/features/attestation.md) - * [Consent](social-registry/features/consent.md) - * [SPAR Update for offline enumerations](social-registry/features/spar-update-for-offline-enumerations.md) + * [SPAR Integration for Account Info](social-registry/features/spar-integration-for-account-info.md) * [Self Service Registration Portal](social-registry/features/self-service-registration-portal.md) * [Unique Reference ID](social-registry/features/unique-reference-id.md) - * [ODK Importer](social-registry/features/odk-importer/README.md) - * [📔 User Guide](social-registry/features/odk-importer/user-guide/README.md) - * [📔 Configure and Import ODK Form](social-registry/features/odk-importer/user-guide/configure-and-import-odk-form.md) - * [📔 Import Specific ODK Forms using ODK Instance ID](social-registry/features/odk-importer/user-guide/import-specific-odk-forms-using-odk-instance-id.md) - * [Logging](social-registry/features/logging/README.md) - * [Audit Logs](social-registry/features/logging/audit-log.md) - * [Audit Log - Advanced](social-registry/features/logging/audit-log-advanced.md) - * [ID Authentication](social-registry/features/id-authentication/README.md) - * [📔 User Guides](social-registry/features/id-authentication/user-guides/README.md) - * [📔 Configure eSignet Auth Provider for ID Authentication](pbms/functionality/id-verification/user-guides/configure-esignet-auth-provider-for-id-authentication.md) - * [📔 ID Authentication Process](social-registry/features/id-authentication/user-guides/id-authentication-process.md) - * [📔 eSignet Client Creation](social-registry/features/id-authentication/user-guides/esignet-client-creation.md) + * [Audit Logs](social-registry/features/audit-log.md) * [Versions](social-registry/versions.md) * [Deployment](social-registry/deployment/README.md) * [Domain names and Certificates](social-registry/deployment/domain-names-and-certificates.md) diff --git a/pbms/development/upcoming-features/verifiable-credential-issuance/user-guides/configure-inji-to-download-beneficiary-vcs.md b/pbms/development/upcoming-features/verifiable-credential-issuance/user-guides/configure-inji-to-download-beneficiary-vcs.md index 9c0a446c..9b935e43 100644 --- a/pbms/development/upcoming-features/verifiable-credential-issuance/user-guides/configure-inji-to-download-beneficiary-vcs.md +++ b/pbms/development/upcoming-features/verifiable-credential-issuance/user-guides/configure-inji-to-download-beneficiary-vcs.md @@ -13,7 +13,7 @@ This guide contains the procedure to install and set up the backend required for (Only required for testing. Not required for production.) -1. Create an [eSignet OIDC client](../../../../../social-registry/features/id-authentication/user-guides/esignet-client-creation.md) with the following parameters: +1. Create an [eSignet OIDC client](../../../../../social-registry/features/id-integration/id-authentication/user-guides/esignet-client-creation.md) with the following parameters: * clientId: mimoto-oidc * clientName: Inji Wallet * logoUrl:[https://raw.githubusercontent.com/mosip/mosip-file-server/master/mosip-file-server/inji-model/inji-home-logo.png](https://raw.githubusercontent.com/mosip/mosip-file-server/master/mosip-file-server/inji-model/inji-home-logo.png) @@ -22,7 +22,7 @@ This guide contains the procedure to install and set up the backend required for ### 2. Create OpenG2P Mimoto OIDC Client -1. Create an [eSignet OIDC client](../../../../../social-registry/features/id-authentication/user-guides/esignet-client-creation.md) with the following parameters: +1. Create an [eSignet OIDC client](../../../../../social-registry/features/id-integration/id-authentication/user-guides/esignet-client-creation.md) with the following parameters: * clientId: `openg2p-mimoto-oidc` * clientName: `Inji Wallet` * logoUrl: [https://raw.githubusercontent.com/mosip/mosip-file-server/master/mosip-file-server/inji-model/inji-home-logo.png](https://raw.githubusercontent.com/mosip/mosip-file-server/master/mosip-file-server/inji-model/inji-home-logo.png) diff --git a/social-registry/README.md b/social-registry/README.md index 1701ec69..e2d48678 100644 --- a/social-registry/README.md +++ b/social-registry/README.md @@ -24,7 +24,5 @@ The registry can host demographic data of both individuals and groups (family/ho Social Registry Functional Architecture {% endembed %} -## Feature and functionality -
FeatureFunctionality
Administration/User Management
  • RBAC
  • Roles
  • Users
API
Attestation
Benefit Targeting Methods
ConfigurationsConfiguration of ID Types, Registrant Tags, Gender Types, Relationships, Group Types, and Group Membership Kind are required to define values (enumerations) for the associated fields.
Consent
Data Share
  • CSV
  • APIs (G2P Connect, GraphQL, REST)
Deduplication
  • Identifies and stores the duplicate entries of the recorded registrants' data.
  • Manages duplicate records within separate groups and individual registries.
Document Upload
  • Assists in uploading the mandatory documents required to register for a program
Domain Specific Registries
Dynamic Updates

  • CSV
  • APIs
  • Login-based direct data entry
  • Operators uploading data
  • ODK (Android, agent, offline)
Enumerator
Fayda ID Integration
Geographic
ID Creation
ID Validation and Tokenisation
Individual and Groups
  • Registry of individuals
  • Registry of household and families
  • Entities with group of people, like school, community
Interoperability
Logging
  • Change logs
  • Audit logs
  • System logs
Lock and Unlock
  • Lock record for edit
  • Suggest for edit/update
  • Request for edit/update
  • Unlock for edit/update
Language Support
Monitoring and Reporting
  • Dashboards
  • Real-time data monitoring
Notifications
  • SMS
  • Email
ODK Importer
Privacy and Security
  • Encryption of PII
Record Revision History
Reporting
Registration Portal
Search
  • Fast data search based on parameters of registrants
Search - Open Search
Self Service Registration Portal
Single Sign-On
Social Registry ID
SPAR Update for Offline Enumerations
Unique Reference ID
Verifiable Credentials Issuance
  • Mobile wallet
  • Paper (QR code)
diff --git a/social-registry/features/administration/README.md b/social-registry/features/administration/README.md index 60c75a0d..dce0ef3d 100644 --- a/social-registry/features/administration/README.md +++ b/social-registry/features/administration/README.md @@ -1,4 +1,4 @@ -# Administration / User Management +# User Management 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: @@ -7,14 +7,17 @@ In the Social Registry, user management is typically handled through an administ 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 +## User 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 +The following lists the different users in the Social Registry module along with their roles and responsibilities. +
User RoleRole and Responsibility
Super Administrator

Role

The Super Administrator has the highest level of administrative access.

Responsibility

Total command of the system such as

  • able to configure every option.
  • possesses access to all data, features, and functionalities in the system.
  • able to manage additional administrators and users.
System Administrator

Role

The System Administrator manages the technical and operational aspects of the system.

Responsibility

  • Ensures the system is running smoothly.
  • Creates users, assigns and revokes privileges.
  • Handles technical issues and user support.
  • May share some responsibilities with the Super Administrator but typically focus on the technical side.
  • Manages system updates and maintenance.
Crypto Administrator

Role

The Crypto Administrator plays a crucial role in the system's security module.

Responsibility

  • Manages and secures cryptographic keys.
  • Oversees encryption practices to ensure data security.
  • Ensures data integrity and protection against unauthorised access.
  • Maintains the confidentiality, availability, and integrity of sensitive information.
  • Can decrypt and view individual encrypted records or PII information.
  • Normally, this role is linked to other important roles.
Registrar

Role

The Registrar manages the registration process of individuals in the Social Registry module.

Responsibility

  • Oversees the enrollment of new individuals.
  • Ensures that registration data is accurate and complete.
  • May validate and approve registration applications.
Data Administrator

Role

The Data Administrator manages the data in the Social Registry module.

Responsibility

  • Ensures data integrity and security.
  • Performs data updates and maintenance.
  • Manages data import and export processes.
  • Can create and manage data backups.
Data Validator

Role

The Data Validator ensures the accuracy and validity of the data collected.

Responsibility

  • Reviews and verifies the data entries for accuracy and completeness.
  • Identifies and corrects the errors or inconsistencies in the data.
  • Works closely with Data Administrators to maintain data quality.
  • Raises data correction requirements for Data Collectors or Data Administrators
Data Collector (Registration portal user)

Role

The Data Collector collects data through the registration portal.

Responsibility

  • Uses the online registration portal to collect and input data.
  • Ensures data is accurately entered into the system.
  • May assist individuals with the registration process through the portal.
Data Enumerator
(Same as Data collector but offline)

Role

The Data Enumerator collects data offline, often in the field.

Responsibility

  • Conducts surveys and gathers data from individuals or households.
  • Typically makes use of the tools like ODK or Kobo.
  • Records data manually or using offline tools.
  • Submits collected data to the Data Administrator for integration into the system.
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

  • Supervises Data Collectors using the registration portal.
  • Coordinates data collection activities within the portal to ensure efficiency.
  • Monitors the quality of data being entered into the Registration Portal.
+### Custom configuration for user roles -
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
+
User RoleAddEditApproveEdit count before lockRequest for editEdit request approverApprove edit requestsRequest for correctionCorrection requested to
Super AdministratorYesYesYes-1NANAYesNoNA
System AdministratorNoNoNoNANANANoNoNA
Crypto AdministratorNoNoNoNANANANoNoNA
RegistrarYesYesYes-1NANAYesNoNA
Data AdministratorYesYesNo2YesSuper/System AdministratorYesNoNA
Data ValidatorNoNoYesNANoNANoYesData Collector
Data EnumeratorYesNoNo1YesData Administrator /RegistrarNoNoNA
Data CollectorYesYesNo1YesData Administrator /RegistrarNoNoNA
Data Collection SupervisorYesYesNo1YesData Administrator /RegistrarNoYesData Collector
-The figure below shows below some of the roles or access levels that can be assigned to users +Notes: + +
Edit count before lockDescription
-1The user is free to edit the data without any limitations.
1The user is allowed to make changes to the data only once.
2The user is allowed to make changes to the data two times.
-
diff --git a/social-registry/features/administration/user-roles.md b/social-registry/features/administration/user-roles.md deleted file mode 100644 index c88a43cd..00000000 --- a/social-registry/features/administration/user-roles.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -layout: - title: - visible: true - description: - visible: false - tableOfContents: - visible: true - outline: - visible: true - pagination: - visible: true ---- - -# User Roles - -The following lists the different users in the Social Registry module along with their roles and responsibilities. - -
User RoleRole and Responsibility
Super Administrator

Role

The Super Administrator has the highest level of administrative access.

Responsibility

Total command of the system such as

  • able to configure every option.
  • possesses access to all data, features, and functionalities in the system.
  • able to manage additional administrators and users.
System Administrator

Role

The System Administrator manages the technical and operational aspects of the system.

Responsibility

  • Ensures the system is running smoothly.
  • Creates users, assigns and revokes privileges.
  • Handles technical issues and user support.
  • May share some responsibilities with the Super Administrator but typically focus on the technical side.
  • Manages system updates and maintenance.
Crypto Administrator

Role

The Crypto Administrator plays a crucial role in the system's security module.

Responsibility

  • Manages and secures cryptographic keys.
  • Oversees encryption practices to ensure data security.
  • Ensures data integrity and protection against unauthorised access.
  • Maintains the confidentiality, availability, and integrity of sensitive information.
  • Can decrypt and view individual encrypted records or PII information.
  • Normally, this role is linked to other important roles.
Registrar

Role

The Registrar manages the registration process of individuals in the Social Registry module.

Responsibility

  • Oversees the enrollment of new individuals.
  • Ensures that registration data is accurate and complete.
  • May validate and approve registration applications.
Data Administrator

Role

The Data Administrator manages the data in the Social Registry module.

Responsibility

  • Ensures data integrity and security.
  • Performs data updates and maintenance.
  • Manages data import and export processes.
  • Can create and manage data backups.
Data Validator

Role

The Data Validator ensures the accuracy and validity of the data collected.

Responsibility

  • Reviews and verifies the data entries for accuracy and completeness.
  • Identifies and corrects the errors or inconsistencies in the data.
  • Works closely with Data Administrators to maintain data quality.
  • Raises data correction requirements for Data Collectors or Data Administrators
Data Collector (Registration portal user)

Role

The Data Collector collects data through the registration portal.

Responsibility

  • Uses the online registration portal to collect and input data.
  • Ensures data is accurately entered into the system.
  • May assist individuals with the registration process through the portal.
Data Enumerator
(Same as Data collector but offline)

Role

The Data Enumerator collects data offline, often in the field.

Responsibility

  • Conducts surveys and gathers data from individuals or households.
  • Typically makes use of the tools like ODK or Kobo.
  • Records data manually or using offline tools.
  • Submits collected data to the Data Administrator for integration into the system.
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

  • Supervises Data Collectors using the registration portal.
  • Coordinates data collection activities within the portal to ensure efficiency.
  • Monitors the quality of data being entered into the Registration Portal.
- -### Custom configuration for user roles - -
User RoleAddEditApproveEdit count before lockRequest for editEdit request approverApprove edit requestsRequest for correctionCorrection requested to
Super AdministratorYesYesYes-1NANAYesNoNA
System AdministratorNoNoNoNANANANoNoNA
Crypto AdministratorNoNoNoNANANANoNoNA
RegistrarYesYesYes-1NANAYesNoNA
Data AdministratorYesYesNo2YesSuper/System AdministratorYesNoNA
Data ValidatorNoNoYesNANoNANoYesData Collector
Data EnumeratorYesNoNo1YesData Administrator /RegistrarNoNoNA
Data CollectorYesYesNo1YesData Administrator /RegistrarNoNoNA
Data Collection SupervisorYesYesNo1YesData Administrator /RegistrarNoYesData Collector
- -Notes: - -
Edit count before lockDescription
-1The user is free to edit the data without any limitations.
1The user is allowed to make changes to the data only once.
2The user is allowed to make changes to the data two times.
diff --git a/social-registry/features/attestation.md b/social-registry/features/attestation.md deleted file mode 100644 index bc6a96cb..00000000 --- a/social-registry/features/attestation.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -description: WORK IN PROGRESS ---- - -# Attestation - diff --git a/social-registry/features/logging/audit-log.md b/social-registry/features/audit-log.md similarity index 70% rename from social-registry/features/logging/audit-log.md rename to social-registry/features/audit-log.md index 86ac99f4..69777cd3 100644 --- a/social-registry/features/logging/audit-log.md +++ b/social-registry/features/audit-log.md @@ -12,7 +12,7 @@ layout: visible: true --- -# Audit Log +# Audit Logs **Audit logs** are an essential component of any system that stores sensitive data. They help in monitoring user activity, recording actions such as login attempts, changing user accounts, updating records, any message added to the record, notification pushed to the record, request sent and accessing sensitive data. This document provides an overview of audit logs, their importance, and best practices for their implementation. @@ -21,3 +21,16 @@ The basic events logging available in Odoo are: * **Login attempts:** Recording successful and failed login which helps in monitoring user access to the system. * **Changes to user accounts:** Tracking the changes made to user accounts which helps in maintaining the integrity of user profiles and detecting unauthorized modifications. * **Access to sensitive data:** Recording access to sensitive data which ensures that only authorized users can access confidential information. + +## Advanced audit logging + +WORK IN PROGRESS + +System needs to log all events of importance for auditing purposes. These logs should be available for a long period of time (as per policy) and it should be possible to retrieve them on demand. + +* Level 1 : Basic timestamp, user on created and last updated (P1) +* Level 2 : Detailed logging of each and every action + +### Design + +It is proposed that MOSIP's Auditmanager service is used for auditin diff --git a/social-registry/features/consent.md b/social-registry/features/consent.md deleted file mode 100644 index 25051a06..00000000 --- a/social-registry/features/consent.md +++ /dev/null @@ -1,2 +0,0 @@ -# Consent - diff --git a/social-registry/features/deduplication/README.md b/social-registry/features/deduplication/README.md index 46e84fd1..5b111e16 100644 --- a/social-registry/features/deduplication/README.md +++ b/social-registry/features/deduplication/README.md @@ -14,7 +14,7 @@ layout: # Deduplication -In Social Registry (SR), the data are received and recorded in several ways. SR is dynamically updated via APIs, Service Provider Portal, ODK, Login-based direct data entry, and so on. In order to maintain the data integrity in SR, a process is a must to ensure the uniqueness and accuracy of the recorded registrants' data. SR has a solution/feature named _**Deduplication**_. +In Social Registry (SR), the data are received and recorded in several ways. SR is dynamically updated via APIs, Service Provider Portal, ODK, Login-based direct data entry, etc. To maintain the data integrity in SR, a process is a must to ensure the uniqueness and accuracy of the recorded registrants' data. SR has a solution/feature named _**Deduplication**_. ## Deduplication @@ -22,7 +22,7 @@ _**Deduplication**_ is the process that identifies and stores the duplicate entr ## ID-based deduplication -ID-based deduplication is a method that detects duplicates based on unique identifiers i.e., IDs assigned to each recorded registrant belong to an individual/group. This method ensures each ID is distinct and helps to maintain single entry for each recorded registrant. In this way, it eliminates redundancies and keeps the database more reliable, clean, and efficient. +ID-based deduplication is a method that detects duplicates based on unique identifiers i.e., functional ID or National ID assigned to each recorded registrant belonging to an individual/group. This method ensures each ID is distinct and helps to maintain a single entry for each recorded registrant. In this way, it eliminates redundancies and keeps the database more reliable, clean, and efficient. To know more about Odoo merge and deduplication, [click here](https://hibou.io/docs/contacts-64/merging-deduplicating-contacts-in-odoo-12-13-331) diff --git a/social-registry/features/domain-specific-registries.md b/social-registry/features/domain-specific-registries.md deleted file mode 100644 index 0ef65766..00000000 --- a/social-registry/features/domain-specific-registries.md +++ /dev/null @@ -1,2 +0,0 @@ -# Domain Specific Registries - diff --git a/social-registry/features/enumerator/README.md b/social-registry/features/enumerator/README.md index c221e77a..238c692f 100644 --- a/social-registry/features/enumerator/README.md +++ b/social-registry/features/enumerator/README.md @@ -22,5 +22,6 @@ The activities performed by the Enumerator are given below:
ActivityDescription
Field workRequires to conduct field visits, door-to-door or specific locations visits, and collect data from respondents directly.
Offline data collectionUses the ODK Collect application to collect data offline. This data is then managed on ODK Central, enables the organizations to access and analyze it easily, even if it was collected offline.
Data managementInvolves in basic data management tasks, such as organizing collected data, checking for completeness and consistency, and entering data into databases or forms.
Region-based data collectionAssigns specific regions or areas for data collection, ensuring comprehensive coverage and efficient data gathering within designated geographical boundaries.
Adding dataCollects information present on the ODK forms. These information ranges from demographic data of individuals, groups of household to social and economic conditions.
+## Enumerator ID - +See details [here](enumerator-id.md). diff --git a/social-registry/features/enumerator/enumerator-id.md b/social-registry/features/enumerator/enumerator-id.md index c674f244..0512fa3e 100644 --- a/social-registry/features/enumerator/enumerator-id.md +++ b/social-registry/features/enumerator/enumerator-id.md @@ -1,6 +1,6 @@ # Enumerator ID -Enumerators are created in the Social Registry (SR) using the Registration Portal. Enumerators are field employees or agents who assist in gathering information from registrants/applicants. Each time an Enumerator is added to the Registration Portal, a unique ID is automatically generated and assigned to them. The assigned ID is the Enumerator ID (EID) which serves as a unique identifier for each enumerator in the SR. +When an [Enumerator](./) is added to the Registration Portal, a unique ID is automatically generated and assigned. This ID is the Enumerator ID (EID) which serves as a unique identifier for each enumerator in the SR. The Data Administrator and the System Administrator have the authority to create Enumerators in SR using the Registration Portal. diff --git a/social-registry/features/id-creation.md b/social-registry/features/id-creation.md deleted file mode 100644 index 00ba7395..00000000 --- a/social-registry/features/id-creation.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -description: Work in progress ---- - -# ID Creation - -Social Registry (SR) maintains the demographic information of individuals, entities, and groups.\ -Once the registrant enters the social registry system, it must generate an SR ID for all registries to distinguish personality and eliminate a huge volume of duplicate entities in the database. The generated ID must be unique across the region. - -
EntityDescriptionRemark
Static prefixRepresents the functional feature

For example,

- SR is the static prefix for the Social Registry.

- FR is the static prefix for the Farmer Registry.

Dynamic prefixRepresents the area of the registrantFor example, If the region is Tigray, then the ID prefix for Farmer Registry is FR-TI
NumericEight digits randomized numeric valueExample: 12435456
- -\ diff --git a/social-registry/features/id-integration/README.md b/social-registry/features/id-integration/README.md new file mode 100644 index 00000000..badf4b56 --- /dev/null +++ b/social-registry/features/id-integration/README.md @@ -0,0 +1,2 @@ +# ID Integration + diff --git a/social-registry/features/fayda-id-integration.md b/social-registry/features/id-integration/fayda-id-integration.md similarity index 100% rename from social-registry/features/fayda-id-integration.md rename to social-registry/features/id-integration/fayda-id-integration.md diff --git a/social-registry/features/id-authentication/README.md b/social-registry/features/id-integration/id-authentication/README.md similarity index 83% rename from social-registry/features/id-authentication/README.md rename to social-registry/features/id-integration/id-authentication/README.md index 38861b55..1644a87f 100644 --- a/social-registry/features/id-authentication/README.md +++ b/social-registry/features/id-integration/id-authentication/README.md @@ -14,11 +14,11 @@ The ID Authentication feature avoids the need for self-authentication via self-s ## Source code -[G2P Auth: OIDC - Reg ID](../../../pbms/development/odoo-modules/authentication-oidc-reg-id.md) +[G2P Auth: OIDC - Reg ID](../../../../pbms/development/odoo-modules/authentication-oidc-reg-id.md) ## Related user guides -:notebook\_with\_decorative\_cover:[Configure eSignet Auth Provider for ID Authentication](../../../pbms/functionality/id-verification/user-guides/configure-esignet-auth-provider-for-id-authentication.md) +:notebook\_with\_decorative\_cover:[Configure eSignet Auth Provider for ID Authentication](user-guides/configure-esignet-auth-provider-for-id-authentication.md) :notebook\_with\_decorative\_cover:[ID Authentication Process](user-guides/id-authentication-process.md) diff --git a/social-registry/features/id-authentication/user-guides/README.md b/social-registry/features/id-integration/id-authentication/user-guides/README.md similarity index 100% rename from social-registry/features/id-authentication/user-guides/README.md rename to social-registry/features/id-integration/id-authentication/user-guides/README.md diff --git a/pbms/functionality/id-verification/user-guides/configure-esignet-auth-provider-for-id-authentication.md b/social-registry/features/id-integration/id-authentication/user-guides/configure-esignet-auth-provider-for-id-authentication.md similarity index 77% rename from pbms/functionality/id-verification/user-guides/configure-esignet-auth-provider-for-id-authentication.md rename to social-registry/features/id-integration/id-authentication/user-guides/configure-esignet-auth-provider-for-id-authentication.md index 63ce15ec..612d8785 100644 --- a/pbms/functionality/id-verification/user-guides/configure-esignet-auth-provider-for-id-authentication.md +++ b/social-registry/features/id-integration/id-authentication/user-guides/configure-esignet-auth-provider-for-id-authentication.md @@ -23,30 +23,30 @@ This document provides instructions on how to configure eSignet Authentication P * Allowed redirect URIs of the client must contain `https://socialregistry.your.org/auth_oauth/g2p_registry_id/authenticate` -* Create two ID types on the Registry such as `NATIONAL ID` and `NATIONAL ID TOKEN`. To configure ID types refer the [Configure ID Types](../../beneficiary-management/beneficiary-registry-configurations/user-guides/configure-id-types.md) documentation. -* Install the [OpenID Connect Authentication](../../../development/odoo-modules/openid-connect-authentication.md) and [G2P Auth: OIDC - Reg ID](../../../development/odoo-modules/authentication-oidc-reg-id.md) module. +* Create two ID types on the Registry such as `NATIONAL ID` and `NATIONAL ID TOKEN`. To configure ID types refer the [Configure ID Types](../../../../../pbms/functionality/beneficiary-management/beneficiary-registry-configurations/user-guides/configure-id-types.md) documentation. +* Install the [OpenID Connect Authentication](../../../../../pbms/development/odoo-modules/openid-connect-authentication.md) and [G2P Auth: OIDC - Reg ID](../../../../../pbms/development/odoo-modules/authentication-oidc-reg-id.md) module. ## Procedure -1. Click the main menu icon ![](../../../../.gitbook/assets/main-menu.png) and select _**Settings**_. +1. Click the main menu icon ![](../../../../../.gitbook/assets/main-menu.png) and select _**Settings**_. -
+
The _**Settings**_ screen is displayed. 2. Select the tab _**Users & Companies**_, and click the option _**OAUTH Providers**_. -
+
_**Providers**_ screen is displayed. -
+
3. Click the _**New**_ button. _**Providers New**_ screen is displayed. -
+
4. Enter the values in the respective fields. @@ -58,8 +58,8 @@ Note: The rest of the fields have the default values. -5. Click the icon ![](../../../../.gitbook/assets/save-button.png) to save the changes. +5. Click the icon ![](../../../../../.gitbook/assets/save-button.png) to save the changes. This completes the process of configuring the _**eSignet Authentication Provider**_ in SR. -To know the process on authenticate an individual, refer [ID Authentication Process](../../../../social-registry/features/id-authentication/user-guides/id-authentication-process.md) documentation. +To know the process on authenticate an individual, refer [ID Authentication Process](id-authentication-process.md) documentation. diff --git a/social-registry/features/id-authentication/user-guides/esignet-client-creation.md b/social-registry/features/id-integration/id-authentication/user-guides/esignet-client-creation.md similarity index 100% rename from social-registry/features/id-authentication/user-guides/esignet-client-creation.md rename to social-registry/features/id-integration/id-authentication/user-guides/esignet-client-creation.md diff --git a/social-registry/features/id-authentication/user-guides/id-authentication-process.md b/social-registry/features/id-integration/id-authentication/user-guides/id-authentication-process.md similarity index 75% rename from social-registry/features/id-authentication/user-guides/id-authentication-process.md rename to social-registry/features/id-integration/id-authentication/user-guides/id-authentication-process.md index 089c5692..92bdd6c3 100644 --- a/social-registry/features/id-authentication/user-guides/id-authentication-process.md +++ b/social-registry/features/id-integration/id-authentication/user-guides/id-authentication-process.md @@ -13,18 +13,18 @@ This document provides instructions to perform ID authentication of an individua ## Procedure -1. Click the main menu icon ![](../../../../.gitbook/assets/main-menu.png) and select _**Social**_ _**Registry**_. +1. Click the main menu icon ![](../../../../../.gitbook/assets/main-menu.png) and select _**Social**_ _**Registry**_. _**Social Registry**_ screen is displayed 2. Click the Individual tab in the menu bar. 3. Select the individual to perform ID authentication. -
+
Individual screen is displayed. -
+
4. Select the IDs tab. 5. Click the _**Authenticate**_ button. diff --git a/social-registry/development/upcoming-features/tokenisation.md b/social-registry/features/id-integration/tokenisation.md similarity index 85% rename from social-registry/development/upcoming-features/tokenisation.md rename to social-registry/features/id-integration/tokenisation.md index d1354e0d..fb13b7aa 100644 --- a/social-registry/development/upcoming-features/tokenisation.md +++ b/social-registry/features/id-integration/tokenisation.md @@ -2,9 +2,9 @@ description: WORK IN PROGRESS --- -# Tokenisation +# ID Validation and Tokenisation -The tokenisation process involves using the [IDA](https://docs.mosip.io/1.2.0/id-authentication) (ID Authentication) system to verify the registrant's data. If the IDs such as registrant's ID (RID), virtual ID (VID), or unique identification number (UIN) are valid, then the IDA system generates a token. The generated token replaces the sensitive data, like RID, VID, or UIN, with non-sensitive data and it is recorded in the database or the individual/group registries of the Social Registry (SR) module. +The tokenisation process involves using the ID Authentication system to verify the registrant's data. If the IDs such as registrant's ID (RID), virtual ID (VID), or unique identification number (UIN) are valid, then the IDA system generates a token. The generated token replaces the sensitive data, like RID, VID, or UIN, with non-sensitive data and it is recorded in the database or the individual/group registries of the Social Registry (SR) module. ## Functionality diff --git a/social-registry/features/individuals-and-groups/README.md b/social-registry/features/individuals-and-groups/README.md index 9593603d..868aa0d6 100644 --- a/social-registry/features/individuals-and-groups/README.md +++ b/social-registry/features/individuals-and-groups/README.md @@ -16,28 +16,22 @@ layout: ## Individual -_**Individuals**_ refer to single persons, each with their own set of demographic data, such as name, date of birth, gender, and other relevant information. The SR can maintain a registry of these individual records, allowing for the management and retrieval of information about each person. +_**Individuals**_ refer to single persons, each with their own set of demographic data, such as name, date of birth, gender, and other relevant information. The SR maintains a registry of these individual records, allowing for managing and retrieving information about each person. -The figure below displays the individual creation page, allowing users to input personal information. - -
+

individual creation page

## Group -_**Groups**_ in the Social Registry (SR) context typically refer to collections of individuals who are related or connected in some way. This could include households, families, communities, or other entities that consist of multiple people. - -The figure below displays the household creation page, allowing users to input details about the members and their relationship with the household head. +_**Groups**_ in the Social Registry (SR) context typically refer to collections of individuals who are related or connected in some way. This could include **households, families, communities,** or other entities that consist of multiple people. -
+

Household creation page - head, members, relationships

### Social Registry can house -* **Registry of individuals**: The Social Registry allows the creation of a registry containing demographic data of individual people. This data is privacy-protected, ensuring the confidentiality of personal information. The Social Registry provides advanced features that ensure the registry can easily integrate into a country's digital public infrastructure (DPI). -* **Registry of households and families**: In addition to individuals, the Social Registry can also host demographic data of households and families. This feature enables the tracking and managing of group data, such as family relationships and household compositions. Like individual data, this group data is also privacy-protected. +* **Individuals**: The Social Registry allows the creation of a registry containing demographic data of individual people. This data is privacy-protected, ensuring the confidentiality of personal information. The Social Registry provides advanced features that ensure the registry can easily integrate into a country's digital public infrastructure (DPI). +* **Households and families**: In addition to individuals, the Social Registry can also host demographic data of households and families. This feature enables the tracking and managing of group data, such as family relationships and household compositions. Like individual data, this group data is also privacy-protected. * **Entities with group of people, like schools, and communities**: The Social Registry extends its functionality to entities that consist of groups of people, such as schools or communities. It provides demographic data for these entities, facilitating better management and service provision. - - ## Related user guides :notebook\_with\_decorative\_cover:[Create an Individual Registrant](../../../pbms/functionality/beneficiary-management/beneficiary-registry/user-guides/create-an-individual-registrant.md) diff --git a/social-registry/features/interoperability.md b/social-registry/features/interoperability.md index e79b9f86..205e2245 100644 --- a/social-registry/features/interoperability.md +++ b/social-registry/features/interoperability.md @@ -1,6 +1,3 @@ # Interoperability -[G2P Connect ](https://github.com/G2P-Connect)interface to - -* Pull data from other sources compliant with G2P Connect. -* Share data with other systems. +Refer to [Interoperability](../../interoperability.md). diff --git a/social-registry/features/lock-and-unlock.md b/social-registry/features/lock-and-unlock.md index 504bbf44..0aa0eb92 100644 --- a/social-registry/features/lock-and-unlock.md +++ b/social-registry/features/lock-and-unlock.md @@ -1,5 +1,4 @@ --- -description: WIP layout: title: visible: true @@ -15,27 +14,24 @@ layout: # Lock and Unlock -In Social Registry (SR) huge volumes of data are recorded. There is a need to set a limit to prevent the data from being edited multiple times. If the limit is set, it improves the accuracy of the data. The Social Registry has the Lock, Unlock, and Update features which play a pivotal role in maintaining the efficiency of the recorded data. \ - +In Social Registry (SR) huge volumes of data are recorded. There is a need to set a limit to prevent the data from being edited multiple times. If the limit is set, it improves the accuracy of the data. The Social Registry has the Lock and Unlock feature which plays a pivotal role in maintaining the integrity of the recorded data. ## Lock -The Lock feature prevents data from being edited multiple times. When the records are loaded on SR and SPP, the limit is set to edit the data only once. If the records are edited once, the Lock feature disables the record from being edited again. +The Lock feature prevents data from being edited inadvertently or without appropriate permissions. When the records are loaded on SR and SPP, the limit is set to edit the data only once. If the records are edited once, the Lock feature disables the record from being edited again. ## Unlock -The Super Admin performs the below activities to unlock/lock the record. - -* If there is a need to edit/update the record, the user must send a request with a valid reason to Super Admin. -* The Super Admin validates the reason. If the reason is valid, he/she approves the request. -* Once the Super Admin approves the request, the user can edit/update the records. -* If the Super Admin rejects the request, the record remains locked. - +Records may be unlocked to be edited following the below process: +* The user must send a request with a valid reason to the Admin (with permissions to allow lock/unlock) +* The Admin validates the reason and approves the request. +* The user can then edit/update the records. +* If the request is rejected, the record remains locked. ## Notification -If there are corrections in the records, then a Super Admin user will send a push and an email notification to the user. The email contains the information on the record that needs to be edited/updated. +If there are updates to the records, Admin will send a push and an email notification to the user. The email contains the information on the record that needs to be edited/updated. ## Log diff --git a/social-registry/features/logging/README.md b/social-registry/features/logging/README.md deleted file mode 100644 index 091eef40..00000000 --- a/social-registry/features/logging/README.md +++ /dev/null @@ -1,2 +0,0 @@ -# Logging - diff --git a/social-registry/features/logging/audit-log-advanced.md b/social-registry/features/logging/audit-log-advanced.md deleted file mode 100644 index 6693e012..00000000 --- a/social-registry/features/logging/audit-log-advanced.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -description: WORK IN PROGRESS ---- - -# Audit Log - Advanced - -System needs to log all events of importance for auditing purposes. These logs should be available for a long period of time (as per policy) and it should be possible to retrieve them on demand. - -* Level 1 : Basic timestamp, user on created and last updated (P1) -* Level 2 : Detailed logging of each and every action - -## Design - -It is proposed that MOSIP's Auditmanager service is used for auditing. (TBD). diff --git a/social-registry/features/monitoring-and-reporting.md b/social-registry/features/monitoring-and-reporting.md new file mode 100644 index 00000000..18ec281b --- /dev/null +++ b/social-registry/features/monitoring-and-reporting.md @@ -0,0 +1,3 @@ +# Monitoring and Reporting + +Refer to [Minitoring and Reporting](../../monitoring-and-reporting/). diff --git a/social-registry/features/monitoring-and-reporting/README.md b/social-registry/features/monitoring-and-reporting/README.md deleted file mode 100644 index 04dd24dd..00000000 --- a/social-registry/features/monitoring-and-reporting/README.md +++ /dev/null @@ -1,2 +0,0 @@ -# Monitoring and Reporting - diff --git a/social-registry/features/monitoring-and-reporting/system-logs.md b/social-registry/features/monitoring-and-reporting/system-logs.md deleted file mode 100644 index 4e99b1e7..00000000 --- a/social-registry/features/monitoring-and-reporting/system-logs.md +++ /dev/null @@ -1,3 +0,0 @@ -# System Logs - -Via Logging base infrastructure. diff --git a/social-registry/features/notifications.md b/social-registry/features/notifications.md deleted file mode 100644 index d63f2bdc..00000000 --- a/social-registry/features/notifications.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -layout: - title: - visible: true - description: - visible: false - tableOfContents: - visible: true - outline: - visible: true - pagination: - visible: true ---- - -# Notifications - -Social Registry supports notifying registrants through Email and SMS. diff --git a/social-registry/features/record-revision-history.md b/social-registry/features/record-revision-history.md index c469ffa4..0049d778 100644 --- a/social-registry/features/record-revision-history.md +++ b/social-registry/features/record-revision-history.md @@ -7,7 +7,7 @@ description: WORK IN PROGRESS Any changes/updates to records in the Registry have to be captured by the system. Admins must be able to see the information associated with a registry record on previous dates. Admins must also be able to generate reports of aggregate data for an earlier period. For example, the total number of farmers with more than 10 acres of land as of Dec 2023. {% hint style="info" %} -Revision History is not the same as [Audit Logs](logging/audit-log.md) or [System Log](../../monitoring-and-reporting/logging.md). +Revision History is not the same as [Audit Logs](audit-log.md) or [System Log](../../monitoring-and-reporting/logging.md). {% endhint %} ## Functionality diff --git a/social-registry/features/score-computation.md b/social-registry/features/score-computation.md index 7cdead88..3fcb95af 100644 --- a/social-registry/features/score-computation.md +++ b/social-registry/features/score-computation.md @@ -1,7 +1,3 @@ ---- -description: WORK IN PROGRESS ---- - -# Score Computation +# Computed fields Support for computed fields like PMT, VBT and other scores in the Social Registry itself (rather than computing them in PBMS and storing back in SR). diff --git a/social-registry/features/search-opensearch.md b/social-registry/features/search-opensearch.md deleted file mode 100644 index 3feb0812..00000000 --- a/social-registry/features/search-opensearch.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -description: WORK IN PROGRESS ---- - -# Search - OpenSearch - diff --git a/social-registry/features/search.md b/social-registry/features/search.md deleted file mode 100644 index 8300a94d..00000000 --- a/social-registry/features/search.md +++ /dev/null @@ -1,2 +0,0 @@ -# Search - diff --git a/social-registry/features/single-sign-on.md b/social-registry/features/single-sign-on.md deleted file mode 100644 index 503c4527..00000000 --- a/social-registry/features/single-sign-on.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -description: WORK IN PROGRESS ---- - -# Single Sign-On - -* Admin login to console, reporting etc. -* Keycloak diff --git a/social-registry/features/spar-update-for-offline-enumerations.md b/social-registry/features/spar-integration-for-account-info.md similarity index 97% rename from social-registry/features/spar-update-for-offline-enumerations.md rename to social-registry/features/spar-integration-for-account-info.md index 3aff0628..082c6acb 100644 --- a/social-registry/features/spar-update-for-offline-enumerations.md +++ b/social-registry/features/spar-integration-for-account-info.md @@ -1,9 +1,10 @@ --- +description: WORK IN PROGRESS layout: title: visible: true description: - visible: false + visible: true tableOfContents: visible: true outline: @@ -12,7 +13,7 @@ layout: visible: true --- -# SPAR Update for offline enumerations +# SPAR Integration for Account Info ## Context diff --git a/social-registry/features/unique-reference-id.md b/social-registry/features/unique-reference-id.md index 3ed93c54..51f8d699 100644 --- a/social-registry/features/unique-reference-id.md +++ b/social-registry/features/unique-reference-id.md @@ -1,7 +1,3 @@ ---- -description: Work In Progress ---- - # Unique Reference ID ### Description diff --git a/social-registry/features/verifiable-credentials-issuance.md b/social-registry/features/verifiable-credentials-issuance.md index 6a936cb5..53367708 100644 --- a/social-registry/features/verifiable-credentials-issuance.md +++ b/social-registry/features/verifiable-credentials-issuance.md @@ -1,7 +1,3 @@ ---- -description: WORK IN PROGRESS ---- - # Verifiable Credentials Issuance Social Registry can issue credentials in the form of [Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) (VC). Upon authentication, these can be downloaded into the beneficiary's **digital wallet** or printed on paper as a **QR code.** These credentials indicate that the individual is the member of the Social Registry. Credentials are sometimes also referred to as e-cards, Farmer Registry e-Card, etc. @@ -15,7 +11,7 @@ Social Registry can issue credentials in the form of [Verifiable Credentials](ht ## High-level workflow -
+
## Source code and configuration