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
      • Hotfix Release 19.2
      • Hotfix Release 19.3
      • Hotfix Release 20.1
      • Hotfix Release 20.2
      • Hotfixes Release 20.3
  • 🪝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
  1. DRISTI Platform
  2. Architecture
  3. Architectural and Design Decisions

Detailed Case Access

Case is the primary entity of DRISTI platform. The following defines the access/actions guidelines for a case based on the various stages that it can be in. If a type of stake holder is not mentioned then that person has no access for that stage.

Stake holder
Party to the Case
Access to Case Details

Complainant

Yes

Yes

Complainant's Advocate

Yes

Yes, unless replaced with another advocate

Complainant's Advocate's Clerk

Yes.

Yes, while assigned to the case by the Advocate. If advocate is replaced, this access will get revoked.

Respondent

Yes

Yes, only after joining the case

Respondent's Advocate

Yes

Yes, only after joining the case and unless replaced with another advocate

Respondent's Advocate's Clerk

Yes (Assigned by Advocate)

Yes, After respondent's advocate joins the case and assigned the clerk. If advocate is replaced, this access will get revoked.

Scrutiny Officer

No. First come first serve i.e. all officers can see the cases for review and can pick one of the list.

Yes, at the time of case scrutiny only

Judge

Yes (assigned by Scrutiny officer when the case is sent for registration)

Yes, once has been assigned by Scrutiny officer. Once access is granted, will continue to have access even if case is sent back to litigant/advocate for any updates.

Bench Clerk

No.

Yes, based on assigned Judge

Nyay Mitra

No.

No, but can access payment related details

Stenographer

No.

No, but has access to specific hearing

Note: DRISIT will support Open APIs that will follow their own authentication and access guidelines
PreviousData VisibilityNextCase Numbering

Last updated 7 months ago

🧰