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

Linked-up process for updating user permissions and auth database - DRAFT #991

Open
nickaddy opened this issue Dec 22, 2023 · 1 comment

Comments

@nickaddy
Copy link
Contributor

nickaddy commented Dec 22, 2023

Background
With the new process for user management coming on board, it makes sense to review the user group permissions and the Auth database. In an ideal world, when the permissions or the auth database are updated, e.g. new user added, existing user removed, permission changed, the updates should be made on all databases simultaneously.

User Story
As the Digital Team, I would like the group permissions and auth database to be updated on all 3 admin environments with a single action so that the updates do not have to be made 3 times.

Feature(s) Description

  • Update the permissions database according to the spreadsheet (need to confirm with Ryan that he hasn't already done this)
  • Create cloud function that enables the Digital team to make a single update to permissions db or authorisation (users) db and the change(s) is/are rolled out to the databases on Production, Staging and Develop
  • (Relates to User Management in general) Filter the Exercise team contact dropdowns in Admin to include only staff in either Operations Senior Manager or Operations Team Member groups

Definition of Done
It's done when the Digital team only have to do it once!

User Testing Steps
Internal testing only

  1. Check that the exercise contacts dropdowns only include Ops staff
  2. Check that when updates are made to permissions or auths, they are updated on all 3 databases

Ticket Champion
Nick

@nickaddy
Copy link
Contributor Author

@warrensearle In the new year, can you have a look at point 2 under features pls? I couldn't locate the convo in Slack and couldn't quite recall how you described how it would operate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant