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

Make it easier to find user and organisation when setting roles in Django Admin #92

Closed
lexvand opened this issue Mar 24, 2022 · 3 comments

Comments

@lexvand
Copy link

lexvand commented Mar 24, 2022

When creating a UserOrganisationRole in Django admin you need to select the user and organisation from a dropdown, that only supports quick selection by a username__startswith search by starting to type in the standard Django <select> field. With the growing number of users and organisations this is becoming an increasingly difficult task.

What would help:

  • Being able to search for the foreign key relation (like in a raw_id_field, but without loosing the quick option; is this an option?)
  • By default filter out inactive users

Alternative: Automatically give manager rights to superusers, so they can use the Lizard management page for configuring user accounts and roles instead of the Django admin. 3Di already supports this, but it may be harder to fit in the Lizard authorisation system.

@lexvand
Copy link
Author

lexvand commented Mar 24, 2022

@byrman What do you think about this issue?

@byrman
Copy link
Member

byrman commented Mar 24, 2022

@byrman What do you think about this issue?

Yes, that Admin page has much to be desired. But is it still used? The same can be achieved by sending an invitation?

We can improve on the Admin page, but perhaps we should get rid of lizard-auth-client and move the concept of organisations and roles to Lizard? Most of the lizard-auth-client library is now obsolete?

Automatically give manager rights to superusers

You propose that our superusers will have the manager role in each and every organisation? I don't like that very much. Preferably, we should only be part of NENS, not of external organisations. (Do you see Amazon employees in our Cognito user pool?)

@lexvand
Copy link
Author

lexvand commented May 5, 2022

Issue moved to nens/nens-auth-client #73 via ZenHub

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