bcgov / bcgov/zeva2

ZEVA 2 - User Management

Open
#108 1 comment 0 reactions 0 assignees View on GitHub
Epic
Dominant language
TypeScript
Stars
1
Forks
6
Avg merge
8h 52m
Merged PRs (30d)
33

Description

User Management
**Goal**
Implement a robust user management system that supports authentication and role-based access control for both BCeID (external) and IDIR (internal government) users, ensuring appropriate permissions are enforced across all ZEVA2 functionalities.

**User Types and Roles**
1. IDIR Users (Government)
• Administrator (IDIR)
• Director (IDIR)
• Engineer/Analyst (IDIR)
2. BCeID Users (Regulated Parties)
• Organization Administrator (BCeID)
• Signing Authority (BCeID)
• Compliance Reporting (BCeID)
• Credit Transfers (BCeID)
• Initiative Agreements (BCeID)
• Guest (BCeID)

**Functional Elements**
1. Authentication
• Support login via BCeID and IDIR.
• Ensure secure access to the ZEVA2 system.
2. Role Assignment
• Admins can assign roles to IDIR and BCeID users.
• Role assignment determines access to features and data.
3. Permissions Management
• Each role has a defined set of permissions (e.g., view, create, edit, delete, sign).
• Permissions are scoped to ZEV models, sales submissions, credit transfers, compliance reports, initiative agreements, and file uploads.
4. User and Organization Management
• Admins can view, create, edit, and disable users and organizations.
5. Audit and Traceability
• Track role assignments and changes to user access.
• Maintain logs of user actions for compliance and security.

**Workflow Summary**
1. User logs in using BCeID or IDIR.
2. Admin assigns appropriate role(s) based on user type.
3. User accesses features based on assigned permissions.
4. Admins manage users and organizations as needed.
5. System logs all access and changes for audit purposes.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. Start by mapping the existing authentication, user, organization, role, permission, and audit components, then clarify the BCeID and IDIR integration boundaries and acceptance criteria for each workflow. Done should include verified access controls, administration flows, and audit coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, authorization, backend-api-design, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.