Create email template for blocked user notification

1. Templates should use the Liquid syntax

Create email template for unblocked user notification

1. Templates should use the Liquid syntax

Create send block notification endpoint

1. POST /api/v1/email/send-block

2. Create block TemplateType

3. Receive SendEmailRequestDto as payload

Create send unblock notification endpoint

1. POST /api/v1/email/send-unblock

2. Create unblock TemplateType

3. Receive SendEmailRequestDto as payload

Create block user endpoint

1. Endpoint: POST /api/v1/users/block-user/{cognitoId}

2. Add isBlocked field to user details base interface

   1. The field should be returned in GET user endpoint

3. Use UpdateService to set is blocked to true

4. user notification-service to send email

5. remove user from braze campaings

Create unblock user endpoint

1. Endpoint: POST /api/v1/users/unblock-user/{cognitoId}

2. Use UpdateService to set is blocked to false

3. user notification-service to send email

4. return user to braze campaings

Prevent blocked users from signing in

1. Create UserBlockedError apollo error

   • Return 401 Unauthorized

   • UserNotFoundError for reference

2. Add isBlocked validation in the listed resolvers:

   • createOTP

   • createLoginOTP

   • signInJWT

   • socialLogin

3. User not found validation for reference

Add isBlocked to userDetails type

Create method to block user

1. Should use axios to trigger a request to user service

Create method to unblock user

1. Should use axios to trigger a request to user service

Add isBlocked to userDetails type

Create block status card on customer page

1. Update users package

2. Add isBlocked to user details type in graphql

3. Add isBlocked to customer query in frontend

4. Create card to display user status

Create mutation to block the user

1. Use blockUser exposed in the user package (instantiated insider the user provider)

2. Create auditLog for the customer blocking

   1. Create new audit action block-user

   2. Example of audit log

3. Create block customer permission

   1. Permission: “RBI.supportActions.customer.block”

   2. Add “RBI.supportActions.customer.*” to rolePermissionMapping in agent role for BK,PLK,TH and FHS

Implement block user in front end

1. Create confirmation modal

2. Check if agent has permission to change customer status

   1. TBD: which permission is needed

3. Trigger block mutation on confirmation

Create mutation to unblock the user

1. Use unblockUser exposed in the user package (instantiated insider the user provider)

2. Create auditLog for the customer unblocking

   1. Create new audit action unblock-user

   2. Example of audit log

3. Check if the agent has permission to unblock

   1. Permission: “RBI.supportActions.customer.block”

Implement unblock user in front end

1. Create confirmation modal

2. Check if agent has permission to change customer status

   1. TBD: which permission is needed

3. Trigger unblock mutation on confirmation

Create blocked account modal

Handle UserBlockedError in signIn

1. Option 1

   1. Create onError handler for signIn mutations

   2. If UserBlockedError:

      1. sign out user

      2. display blocked account modal

   3. Add onError parameter to the following signIn mutations

      1. signInWithOtp

      2. signInWithJwt

      3. signInSocialLogin

2. Option 2

   1. Monitor error value of all the mutations listed above with useEffect

   2. If UserBlockedError:

      1. sign out user

      2. display blocked account modal

Validate if user is blocked before proceeding to cart

1. use getMe query to check user status

2. if isBlocked

   1. sign out user

   2. display blocked account modal