-
Notifications
You must be signed in to change notification settings - Fork 37
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
Manage access to Flotilla through user access groups in Azure AD #986
Labels
feature
New feature or request
Comments
Made a request to add Flotilla to accessIT, the ticket is up and added Øystein and Arnt Erik in the watchlist. @oysand |
Right now it is setup like this. @aestene @oysand |
@aestene @oysand - any action here should be close it or do anything further ? Put it in blocked ? |
2 tasks
@oysand and @Afonso-2403 has made a new request for User Access per Installation (User Flotilla Huldra etc.) |
Completed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the new feature you would like to see
It is required to limit access to robots and functionality based on the facility and the role of the person working on it.
Describe the solution you'd like
Suggestion is to create some initial groups to see how well it works and then build from there. Currently we have mission control and admin as groups. We would like to expand upon that to have both mission control and admin groups for each installation.
How will this feature affect the current Threat Model?
This should improve the threat model by making management of access easier and clearer.
The text was updated successfully, but these errors were encountered: