Org level Role Based Permission Control (RBAC) as a workaround for project specific RBAC #11768
Replies: 2 comments
-
|
Your approach of using separate organizations for dev, staging, and prod environments can work as a workaround, but it comes with significant trade-offs.(1) How It WorksIn the open-source version, organization-level RBAC is available, which lets you assign roles like OWNER, ADMIN, MEMBER, and VIEWER at the organization level.(2)(3) By creating three separate organizations (one for each environment), you can control access to each environment independently using these organization-level roles.(2) Important ConsiderationsDrawbacks of Multiple Organizations:(1)
Recommended ApproachThe documentation recommends starting with a single Langfuse deployment and evaluating its scalability and data isolation capabilities.(1) A single deployment with multiple projects (one per environment) is the standard approach, as it centralizes management, scales efficiently, and minimizes infrastructure complexity.(1) Project-Level RBACProject-level RBAC (assigning different roles within specific projects independent of organization roles) is an Enterprise-only feature and requires an Enterprise license.(3)(4) 📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Lucien0907, yes, as Inkeep describes, this setup would work. Alternatively, we can also give you a trial of the Langfuse Enterprise version. If this would be interesting for you, feel free to reach out to us via |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe your question
Our company is considering getting a Langfuse license with some of those nice features of RBAC and protected prompt labels. However we decided to go with the free plan for now as a trial phase and get the enterprise version later.
So now we are trying to build a workaround for project level RBAC as needed for different envs, and we are considering having 3 separate orgs as the dev, staging and prod envs for different permission settings. Would this approach work as intended?
Langfuse Cloud or Self-Hosted?
Self-Hosted
If Self-Hosted
Free plan v3.146.0
If Langfuse Cloud
No response
SDK and integration versions
No response
Pre-Submission Checklist
Beta Was this translation helpful? Give feedback.
All reactions