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

Add RBAC to support read-only users in an org #1321

Open
asasas234 opened this issue May 10, 2023 · 3 comments
Open

Add RBAC to support read-only users in an org #1321

asasas234 opened this issue May 10, 2023 · 3 comments
Labels
area/control-plane kind/feature New feature or request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@asasas234
Copy link

asasas234 commented May 10, 2023

Currently, all users that are invited into an org in Pixie are given admin-level permissions.
Admin users should have the ability to designate other admins, or invite new users with read-only permissions. This will prevent non-administrators from misconfiguring settings, adding other unwanted users, etc.

@MrAta
Copy link
Contributor

MrAta commented May 15, 2023

+1, in an airgap deployment, it seems that by default the invited users are admin by default.

@aimichelle
Copy link
Member

Hi all, Pixie currently does not have RBAC support. In all deployments of Pixie Cloud, all users who join the org will have admin privileges.

In the near future we would like to support both read-only and write-only permissions, along with finer-grained rules such as entity-level, table-level, and column-level RBAC.

@asasas234 , hopefully you don't mind, but I'm going to edit this issue to phrase it as a feature request instead. That way we can track how many others are interested in this feature. Thanks!

@aimichelle aimichelle changed the title How do I control the permissions of invited users in Community Cloud? Add RBAC to support read-only users in an org May 15, 2023
@aimichelle aimichelle added kind/feature New feature or request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. area/control-plane labels May 15, 2023
@asasas234
Copy link
Author

@aimichelle I think only read-only access is needed, because if you have write access, read access is usually required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane kind/feature New feature or request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants