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

Extended admin UI control for users and user institute access #5159

Open
Jakob37 opened this issue Jan 9, 2025 · 2 comments
Open

Extended admin UI control for users and user institute access #5159

Jakob37 opened this issue Jan 9, 2025 · 2 comments

Comments

@Jakob37
Copy link
Collaborator

Jakob37 commented Jan 9, 2025

⚠️ Important: Please avoid sharing any sensitive or personal information, including text or images, in this issue.

Is your feature request related to a problem in the current program to new available techology or software? Please describe and add links/citations if appropriate.

It would be helpful for us if admins could grant and remove institute access from the UI. This would enable non-bioinformaticians to handle users (this is the key need), and would also be convenient for bioinformaticians to not need to do this through the CLI.

It would be useful in general to allow admins adding and removing users through the UI as well.

Describe the solution you'd like

In the global user interface, it could be possible to remove and possibly update institutes for users with per user buttons.

There could also be an "add new user" button.

user_management

For institute specific user lists, there could be "remove access" buttons, and a button allowing to add user access

cust000_users

Additional context

A separate but related question is how to handle user removals. Guess the history should still be there. Maybe they could be deactivated similarly to panels.

I suspect you guys have thought about all of this already :)

@northwestwitch
Copy link
Member

Hi @Jakob37, it shouldn't be complicated. Good suggestion!

@northwestwitch
Copy link
Member

A separate but related question is how to handle user removals. Guess the history should still be there. Maybe they could be deactivated similarly to panels.

I suspect you guys have thought about all of this already :)

I don't think it would be an issue, as there is already a cli command that deletes users: scout delete user

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

No branches or pull requests

2 participants