Admin User

Overview

The Admin Panel provides comprehensive field configuration and document mapping capabilities for a beneficiary app. The system enables Admins to define custom form fields, configure document types, and establish mappings between form fields and document VCs (verification credentials) .

Use Cases

1. Manage Profile Fields

Create, edit, and delete custom fields for user profile

Main Flow:

  1. Admin navigates to Add Fields page

  2. System displays current list of fields in table format

  1. Admin clicks "Add Field" button System opens field creation modal Field creation modal opened with empty form

  1. Admin fills required field information:

  • Label (display name)

  • Name (internal identifier)

  • Type (text, numeric, date, boolean, dropdown)

  • Ordering (display sequence)

  • Required flag

  • Editable flag

  • Options (for dropdown type)

Modal with all field information filled out

  1. Admin clicks Add field button

  2. System validates field data

  3. System calls API to persist field

  4. System refreshes field list

  5. Updated fields table showing newly added field

  6. System displays success confirmation

Alternative Flows:

  • AF-001a: Edit existing field

  • AF-001b: Delete field

Business Rules:

  • Field names must be unique

  • Ordering must be numeric and positive

  • Dropdown fields must have at least one option

  • Fields in use cannot be deleted

2. Configure Document Types

Actor: Beneficiary Admin Goal: Define document types and their VC field schemas for verification

Preconditions:

  • Admin has access to admin panel

  • VC schemas are defined on issuance platform

Main Flow:

  1. Admin navigates to Document Config page

  2. System displays current document configurations

  3. Document Configuration page with existing configurations

  4. Admin reviews/adds document configuration:

    • Document Name (display name)

    • Document Label (user-friendly label)

    • Document Type (category)

    • Document Sub Type (specific identifier)

    • VC Fields (JSON schema defining available fields)

Document configuration form with all required fields

  1. Admin enters all fields

  1. VC Fields textarea with JSON schema input

  2. System validates JSON structure

  3. Admin saves all configurations

Save All Configurations button highlighted

  1. System persists configurations via API

  2. System displays success confirmation

Alternative Flows:

  • AF-002a: Add new document configuration

  • AF-002b: Remove document configuration

    • Admin clicks delete icon

    AF-002b: Delete icon on configuration block

    • System removes configuration from list

  • AF-002c: Invalid JSON format

Business Rules:

  • All document fields are required

  • VC fields must be valid JSON object

  • Each field in VC schema must have a "type" property

  • Document sub types should be unique

3. Map Fields to Documents

Actor: Beneficiary Admin Goal: Create mappings between form fields and document VC fields

Preconditions:

  • Form fields are configured in system

  • Documents are configured with VC schemas

Main Flow:

  1. Admin navigates to Field Mapping Config page

  2. System loads available form fields and document types

Field Mapping Configuration page with loaded data

  1. Admin creates field mapping:

  2. Admin can add multiple document mappings per field

Multiple document mappings for single field

  1. System validates all mappings

  2. Admin saves all mappings

Save All Mappings button highlighted

  1. System persists mapping configuration via API

Success toast with mapping statistics

Alternative Flows:

Business Rules:

  • Each field mapping must have at least one document mapping

  • Document and VC field selections are required

  • Transformation JSON must be valid format

  • Form fields can map to multiple documents/field

Data Flow

Field Management Flow

  1. Load: Fetch existing fields from API

  2. Display: Render fields in table format

  3. Interact: User initiates add/edit/delete

  4. Validate: Client-side validation of input

  5. Submit: API call with validated data

  6. Refresh: Update local state and UI

  7. Feedback: Success/error notification

Document Configuration Flow

  1. Initialize: Load existing configurations

  2. Configure: User enters document details

  3. Validate: JSON schema validation for VC fields

  4. Bulk Save: Submit all configurations together

  5. Persist: Backend storage of configurations

  6. Confirm: Success notification

Field Mapping Flow

  1. Prepare: Load fields and documents

  2. Parse: Extract VC fields from document schemas

  3. Map: User creates field-to-document relationships

  4. Transform: Optional JSON transformation rules

  5. Validate: Ensure all required mappings

  6. Save: Persist mapping configuration

  7. Apply: Mappings available for form processing

PreviousBeneficiary UserNextProvider Toaster

Last updated