Story (Required)

As a user accessing an ApprovalTask
I want the system to validate whether I am an individual approver or part of an approver group
So that I can be presented with the correct approval actions and receive a clear indication of my approver status.

Description:
This story ensures proper validation of the active user’s approver status. It clarifies whether the user is an individual or part of a group approver list and adjusts the available actions and notifications accordingly. This improves the accuracy of user interactions and reduces confusion during approval workflows.

Background (Required)

Currently, the approval task interface does not differentiate between users who are directly assigned as approvers and those who are part of an approver group. As a result, users in a group may not see the correct actions or receive clear validation messages regarding their approver eligibility.
Enhancing this behavior ensures that group members are properly validated, with clear action options and confirmation of their approval rights.

Out of Scope

• Changes to backend approval logic or group membership management

• Notification delivery mechanism beyond the scope of the single user ApprovalTask view

• Modifications to user or group creation flows

Approach (Required)

1. User Validation Logic

• • On loading the ApprovalTask, validate the activeUser:

• • • If activeUser is listed as an individual approver → Treat as individual.

• • • If activeUser is in an approver group → Validate as group member but treat as individual approver for this task.

• • • If activeUser is not in the approver list or any approver group → Mark as “Not in approver list”.

1. UI Changes

• • Display available options:

• • • Approve

• • • Reject

• • Show notification banner confirming validation status:

• • {{}}

1. Technical Path

• • Update user validation logic in frontend helper or middleware layer.

• • Introduce a reusable hook or utility useApproverValidation().

• • Modify ApprovalTask component to:

• • • Consume validation result.

• • • Conditionally render actions and notifications.

Dependencies

• Backend API endpoint that provides user-group membership details.

• Existing ApprovalTask component and data model.

• User context or identity provider integration (for activeUser retrieval).

Acceptance Criteria (Mandatory)

• Validation occurs automatically on load.

• Notifications are clear and non-blocking.

• Unit tests cover all validation paths (individual, group, non-approver).

INVEST Checklist

• ✅ Design is implementable

• ✅ Acceptance criteria agreed upon

• ✅ Story estimated

Done Checklist

• Code is completed, reviewed, documented, and checked in

• Unit and integration tests are implemented and passing

• Continuous Delivery pipelines include new code successfully

• Documentation (user-facing + API) updated

• Acceptance criteria fully met