Dedicated user object which can include groups/teams and other attributes #1154
Replies: 5 comments 6 replies
-
Currently Needs:
Note: this is unrelated to users that have access to projects via the Langfuse UI and thus is not to be confused with the |
Beta Was this translation helpful? Give feedback.
-
To add on to this: I have a use case where each user can belong to multiple groups, so just a single Having the user as an object would solve this but I imagine it would be much harder to build dashboard features that work out-of-the-box with that unless you enforce a certain structure of the object. I like the idea of having user attributes that you can use for filtering though. Posthog let's you do this for example: either via person properties (where the fields are automatically detected and available for filtering) or HogQL via person.properties.$field |
Beta Was this translation helpful? Give feedback.
-
Would be nice to be able to set aliases to users. We are using uuid on user ids and it's not a friendly information for the business and support teams to use in the dashboard. |
Beta Was this translation helpful? Give feedback.
-
what would really be useful is "tenant-id" or "client-id" to segregate different clients using our SaaS. It would be great to easily pass this information to our client's dashboards (because who doesn't want more statistics & graphs ! ;). |
Beta Was this translation helpful? Give feedback.
-
Team would be also very useful for prompt management and access management. Any idea if it will be transform as feature for the next release? |
Beta Was this translation helpful? Give feedback.
-
Describe the feature or potential improvement
-> Users can now belong to a team/group
Uses cases:
Additional information
Maybe we could just add a "group_id" to the traces/generations just like "user_id" ?
Beta Was this translation helpful? Give feedback.
All reactions