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

default permission on new created "software components" #70

Open
nopeppermint opened this issue Jan 22, 2025 · 5 comments
Open

default permission on new created "software components" #70

nopeppermint opened this issue Jan 22, 2025 · 5 comments

Comments

@nopeppermint
Copy link
Contributor

to reproduce:

  • create a user
  • logout
  • login as admin
  • give new created user admin rights
  • logout
  • login as new created user
  • click on home/add software component

Image

Image

  • confirm
  • click on "manage user permissions"
  • search for a user (would be nice to have here a list of registered users displayed..)

Image

  • it seems as default a user with admin rights has only "read" permission on his own created "software component", not sure if this is just wrong displayed or if that's actually what the real permission is

as a user with admin rights I would expect to have full permission on my own created "software component" per default ;-)

@pellecchialuigi
Copy link
Collaborator

Thanks for filing this issue and for explaining the workflow so clear.
Let me say that this behavior is wanted.
As you can see from the form, the level of granularity you can assign is also considering READ permissions.
The default READ permission is True but you can remove READ permission to target users.
The reason behind that is that sometime, depending of your project and customer, you need to sign an NDA to access some information.
The goal of the ADMIN is not to refine the data engineers are working on. His role is to enable/disable users, reset passwords, configure default test configurations and so on.
Does that make sense to you?

And, I totally agree on having the list of users accessible there, good point!

@nopeppermint
Copy link
Contributor Author

Yes, I see.

In less restricted areas, it might simplify life of all users, if permissions of all projects could be changed for a single user at one place. If I understand it right, currently every user has to change his permissions on every project separately.

@pellecchialuigi
Copy link
Collaborator

You got it. That's actual situation.
User management is kind of recent feature in BASIL. We have room of improvements there!
You would like to be able to select a single user and assign to him same permission for multiple software components right?

@nopeppermint
Copy link
Contributor Author

You would like to be able to select a single user and assign to him same permission for multiple software components right?

yes, I think that might be useful.

@pellecchialuigi
Copy link
Collaborator

I'll start simplifying the management of user permission for a single software component.
Then we will figure out ho to clone permissions across different sw components.

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