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

Portfolios and Services RBAC for Organizations and Teams #724

Closed
gianmarco-mameli opened this issue Nov 9, 2023 · 6 comments
Closed

Portfolios and Services RBAC for Organizations and Teams #724

gianmarco-mameli opened this issue Nov 9, 2023 · 6 comments
Milestone

Comments

@gianmarco-mameli
Copy link

Description of the feature
Hi, we would like to filter the visibility of portfolios and/or services based on permission granted to Teams and/or Organizations.
Actually users from different teams and organizations are able to see all the portfolios and services created.

Describe the solution you'd like
Portfolio "A" with Service "A" and "B" only visible to Organization "A"
Portfolio "B" with Service "C" and "D" only visible to Organization "B"
Portfolio "C" with Service "E" and "F" only visible to Team "C"

@Sispheor
Copy link
Contributor

Sispheor commented Nov 9, 2023

Not a bad idea!
We'll see what we can do. Seems that technically the "Portfolio" model is not linked to permission or scope. We'll evaluate the possibility of implementing your idea and let you know.
Thanks !

@amitchettri
Copy link

This would very useful feature. Hopefully this can be added.

@Sispheor Sispheor added this to the v2.7 milestone Aug 2, 2024
@Sispheor
Copy link
Contributor

Done

@amitchettri
Copy link

amitchettri commented Dec 16, 2024

could we also possibly see some possible updates on #788

@amitchettri
Copy link

@Sispheor I was checking on the GitHub page for instructions on how we do this, but it seems to be missing or I could not find it.

Can you help me with some information on how this work?

@Sispheor
Copy link
Contributor

Just a line added in the Operation table in the doc. You just need to set a perm on each operation.

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

No branches or pull requests

3 participants