As a GC Notify user, I need to be able to see which team members on my service are inactive from looking at the UI in Notify so that I can manage my team, manage risk for my service and ensure employees who have left the team no longer have the ability to sign in and use the service.
WHY are we building?
We learned that if a user is set to inactive, they can no longer sign in to GC Notify, but they still appear in the team members list for services they were members of and there was no indication this user was inactive
WHAT are we building?
An indication in the UI that a user is inactive on the team members page
VALUE created by our solution
Better UX for those manage team members in Notify to have assurance that inactive team members do not still have accesss to their services.
Description
As a GC Notify user, I need to be able to see which team members on my service are inactive from looking at the UI in Notify so that I can manage my team, manage risk for my service and ensure employees who have left the team no longer have the ability to sign in and use the service.
WHY are we building? We learned that if a user is set to inactive, they can no longer sign in to GC Notify, but they still appear in the team members list for services they were members of and there was no indication this user was inactive WHAT are we building? An indication in the UI that a user is inactive on the team members page VALUE created by our solution Better UX for those manage team members in Notify to have assurance that inactive team members do not still have accesss to their services.
Documentation and Artifacts
Action item from incident https://docs.google.com/document/d/1U6aRK2ZXnsQka5FPY7e3iJOFP1hnXWYW1SJWMqa_iwQ/edit
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics
Related Research Airtable records
QA Steps