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

Implement Super Admin User Feature #1747

Open
4 of 11 tasks
Tracked by #1737
JackHaeg opened this issue Sep 17, 2024 · 0 comments · May be fixed by #1765
Open
4 of 11 tasks
Tracked by #1737

Implement Super Admin User Feature #1747

JackHaeg opened this issue Sep 17, 2024 · 0 comments · May be fixed by #1765
Assignees
Labels
p-feature: User Permissions Feature includes how user access levels / user permissions will be implemented in the product role: Back End role: Front End size: 1pt Can be done in 4-6 hours

Comments

@JackHaeg
Copy link
Member

JackHaeg commented Sep 17, 2024

Overview

With the introduction of admin user promotion and demotion capabilities in VRMS (see #1746), it’s critical that we implement safeguards to prevent the removal or modification of permissions by a rogue admin. To ensure the security of admin permissions, we’ve decided to create a dedicated super admin account ([email protected]) that is immune to modifications by other admin users. This account will have locked admin status, which cannot be altered. When another admin accesses the super admin’s EditUser page, the page will be view-only, preventing any changes while maintaining visibility.

Action Items

  • Create user on Dev and Prod with ([email protected])
  • Promote user to Admin on Dev (Josh)
  • Promote user to Admin on Prod (Josh)
  • @ntrehan to discuss with @trillium & @jbubar how to implement this feature
  • Use email address to identify/filter user: [email protected] (reasoning - this user has different names on Dev and Prod, but the same email is used - "VRMS ADMIN" on Prod, & "VRMS VRMS" on Dev currently).
  • WHEN another admin user is viewing the super admin's "EditUser's" page, Disable features from being edited on the super admin's page (i.e., make the page "view-only" when viewed by another admin user):
    • "Is Active",
    • "VRMS Admin",
    • "Remove" Project function (once a project has been added to the user's profile, the user is ,
    • "Select a project"
  • WHEN the super admin user ([email protected]) is editing their own page, all of these features should be enabled.

Resources/Instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p-feature: User Permissions Feature includes how user access levels / user permissions will be implemented in the product role: Back End role: Front End size: 1pt Can be done in 4-6 hours
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

2 participants