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

Allow for multiple user roles #1361

Open
38 tasks
r-bartlett-gsa opened this issue Jul 1, 2024 · 0 comments
Open
38 tasks

Allow for multiple user roles #1361

r-bartlett-gsa opened this issue Jul 1, 2024 · 0 comments
Labels

Comments

@r-bartlett-gsa
Copy link
Member

r-bartlett-gsa commented Jul 1, 2024

User story

As an admin user who's managing user roles and permissions, in order to allow users to complete tasks associated with multiple roles, I would like to be able to select/assign more than one role to a user.

Acceptance criteria:

  • An admin user can select multiple choices for non-admin user roles (challenge manager, evaluator, public solver)
  • A user has appropriate permissions and access to appropriate Challenge.gov sections associated with all their assigned roles

For reference, current user account roles:

  • Super admin - Can only be added by other Super Admin; Can control all aspects of system;
  • Admin - Can only be added by other Admins or a Super Admin; can assign Challenge Manager to multiple challenges
  • Challenge manager - approved by an admin, requires annual certification; given access with .gov or .mil email address. Admins can give challenge manager access to non-gov or non-mil accounts if a sponsorship/justification is provided by a federal employee.
  • Public solver - all non-.gov or .mil email addresses; not required to do annual certification
  • (NEW) Evaluator - approved by an admin, requires annual certification; given access with .gov or .mil email address. Admins can give challenge manager access to non-gov or non-mil accounts if a sponsorship/justification is provided by a federal employee. (see New user role: Evaluator #1360)

Definition of Done

Doing (dev team)

  • Code complete
  • Code is organized appropriately
  • Any known trade offs are documented in the associated GH issue
  • Code is documented, modules, shared functions, etc.
  • Automated testing has been added or updated in response to changes in this PR
  • The feature is smoke tested to confirm it meets requirements
  • Database changes have been peer reviewed for index changes and performance bottlenecks
  • PR that changes or adds UI
    • include a screenshot of the WAVE report for the altered pages
    • Confirm changes were validated for mobile responsiveness
  • PR approved / Peer reviewed
  • Security scans passed
  • Automate accessibility tests passed
  • Build process and deployment is automated and repeatable
  • Feature toggles if appropriate
  • Deploy to staging
  • Move card to testing column in the board

Staging

  • Accessibility tested (Marni)
    • Keyboard navigation
    • Focus confirmed
    • Color contrast compliance
    • Screen reader testing
  • Usability testing: mobile and desktop (Tracy or Marni)
  • Cross browser testing - UI rendering is performant on below listed devices/browsers (Tracy or Marni)
    • Windows/Chrome
    • Windows/Edge
    • Mac/Chrome
    • Mac/Safari
    • iOS/Safari
  • AC review (Renata)
  • Deploy to production (production-like environment for eval capability) (dev team)
  • Move to production column in the board

Production

  • User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
  • PO / PM approved (Jarah or Renata)
  • AC is met and it works as expected (Jarah or Renata)
  • Move to done column in the board (Jarah or Renata)
@r-bartlett-gsa r-bartlett-gsa changed the title Allow for multi user roles WIP_ Allow for multi user roles Jul 1, 2024
@r-bartlett-gsa r-bartlett-gsa changed the title WIP_ Allow for multi user roles Allow for multiple user roles Jul 3, 2024
@r-bartlett-gsa r-bartlett-gsa transferred this issue from GSA/Challenge_platform Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant