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

feat: teams #2924

Open
tjbck opened this issue Jun 8, 2024 · 7 comments
Open

feat: teams #2924

tjbck opened this issue Jun 8, 2024 · 7 comments
Assignees
Milestone

Comments

@tjbck
Copy link
Contributor

tjbck commented Jun 8, 2024

user group

@mindspawn
Copy link
Contributor

So glad to see a 0.4.0 target release :) can't wait.

@mindspawn
Copy link
Contributor

Hopefully the notion of teams propagates to chromadb queries as well so that each team can have its own set of documents. Also having a way to have some documents shared among all teams would also be great.

@tjbck
Copy link
Contributor Author

tjbck commented Jun 9, 2024

might get delayed to v0.5.0 depending on my availability 😅

@mindspawn
Copy link
Contributor

haha. No worries. Completely understandable :)

@jannikstdl
Copy link
Contributor

Related #715

@flefevre
Copy link

Just to understand your 'Hopefully the notion of teams propagates to chromadb queries'
Foes that mean each team has its own setup for chroma instance tenant etc . Ensuring good separation.

@Moisebala
Copy link

Implements a new access control system that allows for granular permissions on specific models without granting full admin rights to users. The main features should include:

  1. Creation of user groups with customizable access levels
  2. Ability to assign specific models to user groups
  3. Implementation of a permission checking mechanism for model access
  4. Updates to the user interface to reflect these new permissions

This feature must enhances security and flexibility by allowing administrators to grant limited access to certain models or functionalities without compromising overall system integrity. It addresses the need for more nuanced user roles beyond the binary admin/non-admin distinction.

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

5 participants