DRISTI
  • 👋Welcome to DRISTI
    • Why DRISTI?
  • ⚖️About DRISTI
    • Overview
    • Design Principles
    • Value Proposition
    • Architecture Overview
    • System Users
    • Key Modules
      • Async Applications & Submissions
        • Key Features
        • Process & Workflows
        • Specifications
      • Case Management
        • Key Features
        • Process & Workflows
        • Specifications
      • E-Filling, Scrutiny and Admission
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Evidence
        • Key Features
        • Process & Workflows
        • Specifications
      • Listing & Scheduling
        • Key Features
        • Process & Workflows
        • Specifications
      • Hearings
        • Key Features
        • Process & Workflows
        • Specifications
      • Orders & Tasks
        • Key Features
        • Process & Workflows
        • Specifications
      • Summons, Bails, Warrants
        • Key Features
        • Process & Workflows
        • Specifications
      • User Benefits
      • User Registration
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Roles per Module
    • API Specifications
    • Security
    • Privacy
  • 🧰DRISTI Platform
    • Architecture
      • Overview
      • Principles
      • High Level Design
        • Technology Stack
        • Access Control & Roles
        • Data & Analytics
        • Non Functional Requirements
          • Performance
          • Security
          • Data Retention
        • Logging Guidelines
      • Low Level Design
        • Advocate
          • Advocate - API Specifications
          • Sequence Diagram
        • Application
          • Application - API Specifications
          • Sequence Diagram
        • Case
          • Case - API Specifications
          • Sequence Diagram
        • Case Management
          • Case Management - API Specifications
          • Sequence Diagram
        • Evidence
          • Evidence - API Specifications
          • Sequence Diagram
        • Hearing
          • Hearing - API Specifications
          • Sequence Diagram
        • Order
          • Order - API Specifications
          • Sequence Diagram
        • Task
          • Task - API Specifications
          • Sequence Diagram
          • Summons
          • Warrant
      • Architectural and Design Decisions
        • Data Visibility
        • Detailed Case Access
        • Case Numbering
          • Filing Number
          • Court Case Number
          • CNR Number
          • Case Stages, Numbers & Dates
    • Interoperability
    • Release Notes
      • Release 1.1.0
      • Release 1.2.0
      • Release 1.3.0
      • Release 1.4.0
      • Release 1.5.0
      • Release 1.6.0
    • Hotfixes
      • Hotfix Release 17.3
      • Hotfix Release 18.1
      • Hotfix Release 18.2
      • Hotfix Release 18.3
      • Hotfix Release 18.4
      • Hotfix Release 19.1
  • 🪝Setup
    • Planning DRISTI Implementation
    • Establish Project & Team
    • Gather Requirements
    • Installation
      • Infrastructure Setup
        • Azure Setup
        • SDC - OpenShift Setup
      • Code Deployment
      • Configuration
        • Functional Configuration
        • Service Configuration
          • Court
            • Court UI
          • Case
            • Case UI
          • Advocate
            • Advocate UI
          • Application
            • Application UI
          • Task
            • Task UI
          • Order
            • Order UI
          • Hearing
            • Hearing UI
          • Evidence
            • Evidence UI
    • Quality Assurance Testing
    • Go Live
    • Operational Support
    • Monitoring
  • 🛣️Roadmap & Updates
    • Roadmap
  • 🌾Resources
    • Source Code
    • Technology Stack
    • Licensing
    • Legal Taxonomy
  • 🌐COMMUNITY
    • Interested in Contributing?
    • Github Discussion
    • Code of Conduct
  • 🪝Setup
    • Coming soon...
    • 🟢ABOUT US
Powered by GitBook
On this page
  • Assumptions
  • Litigant Registration
  • Advocate Registration
  • Advocate Clerk Registration
  • Notifications
  • Employees
  • Login
  • Ideas for Future Development
  • UI Screens
  1. About DRISTI
  2. Key Modules
  3. User Registration

Specifications

Assumptions

Theme
Assumption

Advocate Registration

Advocates once registered will not be deactivated through the system. Advocates can be disabled through the backend.

Litigant/Advocate Registration

All users have a valid mobile number that can receive OTPs.

Advocate Clerk Rights

Advocate Clerks can only view the case and cannot perform actions

Litigant Registration

  1. Litigants can create an account using their Mobile number (OTP verification).

  2. Registration based on the mobile number will be unique, with only one registration per mobile number.

  3. On the first login, individuals have to fill out a registration form with their details.

    • They can verify their identity using Aadhar or upload an ID card. The Nyay Mitra team will check these details.

    • Once the form is filled, individuals will be given access to the home page with the option to file a case, view cases etc.

  4. If the individual drops out before registering, the user will log in to a home screen where the only card the user will see is to complete the registration.

Advocate Registration

  1. Advocates can create an account using their Mobile number (OTP verification).

  2. Registration based on the mobile number will be unique, with only one registration per mobile number.

  3. On the first login, advocates, similar to individuals, will be required to fill out a registration form with their details -

    • Advocates will have the option to verify their identity using their Aadhar or upload an ID card.

    • Additionally, Advocates will have to provide their BAR registration details.

    • Once the form is filled, the approval workflow will be triggered.

    • The registration approver will be able to view all registration requests in their inbox and will be able to approve/reject a request.

    • Rejection of a request will require remarks to be mandatorily added by the registration approver.

    • Upon approval, advocates will be given access to the home page with the option to file a case, view cases etc.

  4. In case the advocate drops out before registering, the user will log in to a home screen where the only card the user will see is to register.

  5. Advocates can view their application status in their My Applications section.

Advocate Clerk Registration

The Advocate Clerk registration process is the same as the Advocate registration except that they will not have to provide a BAR ID.

Notifications

The following SMS notifications are to be triggered during the workflow:

  1. The Advocate will receive an SMS notification on approval of their Registration Request.

Employees

  1. Employees can log in to the system using a username and password.

  2. After logging in, they can review all the pending registrations for advocates and advocate clerks and approve/reject them.

Login

  1. There will be a separate login URL for Litigants/Advocates and a separate login URL for employees.

  2. Users should stay logged in on the mobile app and web browser after logging in.

Ideas for Future Development

  1. Aadhar verification

  2. Auto-approval of verification of litigants

  3. OCR verification of uploaded documents

UI Screens

  1. Sample Litigant Registration Flow on Mobile

PreviousProcess & WorkflowsNextSequence Diagrams

Last updated 9 months ago

⚖️
Sample Litigant Registration Flow