Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notification of successful user disabling #2102

Open
9 tasks
Tracked by #2100
tdonaworth opened this issue Mar 21, 2024 · 0 comments
Open
9 tasks
Tracked by #2100

Notification of successful user disabling #2102

tdonaworth opened this issue Mar 21, 2024 · 0 comments
Labels
Dev Backend Ready Backend, Pipeline, or other UX related work is refined, and ready for Developers security-privacy-compliance Work needed around Security, Privacy, or Compliance story A defined user story adhering to expected norms including a narrative

Comments

@tdonaworth
Copy link
Contributor

tdonaworth commented Mar 21, 2024

User Story

As a user with the User Admin role, I need to be notified when a user has been disabled automatically or by any other User Admin in order to fulfill compliance requirements.

Acceptance Criteria

  • When the automated processes from Automatically Disable Inactive OPS Accounts #2104 automatically set a user to INACTIVE, all User Admins should receive a notification in OPS of this event with the relevant details. See note in the last section of the story
  • When another user with the User Admin role sets another user to LOCKED (or INACTIVE), all other User Admins should receive a notification in OPS of this event with the relevant details. See note in the last section of the story

Tasks

UX

  • Shouldn't be any new UX needs for this

Dev

Definition of Done Checklist

  • UI works as designed (UX team)
  • PR(s) have been merged to main
  • Design/tech debt eliminated
  • New design/tech debt documented (if applicable)
  • Build process updated
  • Documentation updated or added
  • Feature flags/toggles created

Additional Context & Resources

  • This is required for compliance reasons for AC-02 (1)
  • **Ideally email would be nice and will eventually be required, but internal OPS notifications can suffice for now
@tdonaworth tdonaworth added the task task for an associated story or backlog item label Mar 21, 2024
@jonnalley jonnalley added story A defined user story adhering to expected norms including a narrative security-privacy-compliance Work needed around Security, Privacy, or Compliance Dev Backend Ready Backend, Pipeline, or other UX related work is refined, and ready for Developers and removed task task for an associated story or backlog item labels Oct 15, 2024
@jonnalley jonnalley changed the title ac-02-01 - Automated Account Activities ac-02-01 - Notification of disabling Oct 15, 2024
@jonnalley jonnalley changed the title ac-02-01 - Notification of disabling Notification of successful user disabling Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev Backend Ready Backend, Pipeline, or other UX related work is refined, and ready for Developers security-privacy-compliance Work needed around Security, Privacy, or Compliance story A defined user story adhering to expected norms including a narrative
Projects
None yet
Development

No branches or pull requests

2 participants