UI Permissions

[piclemx]

Problem

Current, every user after login seems to have access to each namespace.

It would have been interesting to have a way to segregate access of users base on something.

Ideal Solution

• Ability to map a user to a given namespace
• Ability to give read/write permission to a given namespace

Search

• I searched for other open and closed issues before opening this

Additional Context

No response

[markphelps]

What if we added support for Open Policy evaluation in Flipt. This would allow orgs to define their own policies to fit their needs and we could pull them in during runtime. We could have some pre-configured (RBAC) policies potentially built into Flipt itself. We would need to figure out how to map authenticated users with these policies though

[piclemx]

What if we added support for Open Policy evaluation in Flipt. This would allow orgs to define their own policies to fit their needs and we could pull them in during runtime. We could have some pre-configured (RBAC) policies potentially built into Flipt itself. We would need to figure out how to map authenticated users with these policies though

So we would need to deploy our own OPA?

[markphelps]

No they expose a library that is written in go so we can evaluate the policies in Flipt. No extra services needed.

We will need to figure out a nice way to allow users to configure their own policies that can be loaded at startup and map them to some standard roles that we define (I think). Also rego may be a non starter for some as it's got a bit of a learning curve, but would love to hear your thoughts

[piclemx]

I loved the idea.