Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4356] [FEAT]: User control of RAG database in a single workspace #2777

New Issue
Closed
opened 2026-02-22 18:31:12 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:31:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @jhsmith409 on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4356

What would you like to see?

I realize this may be better handled by a more complete solution for RBAC across all of anythingLLM. I've read a number of feature requests looking for either the full RBAC solution or bits and pieces.

So, far I have not seen anyone taking on the full task of RBAC. If I were to do that, I would look to using a database that supported that function for me which then becomes a huge project of changing the internal database of anythingLLM. This is complicated by RBAC being a paid feature in many databases.

So short of full RBAC implementation, I, like others, am seeing limits where I can apply anythingLLM. I've seen Tim reject (and with good reason) other partial user permission enhancements that did not offer a full set of features. Despite this, my intention is to create a fork for User-based control of the RAG in a single Workspace and hope Tim will accept that back in. If not, I'll end out with a fork I have to maintain until full RBAC is implemented. Hoping with the right features, Tim would be willing to merge this back in before RBAC is implemented.

(Fishing for comments from Tim as to what he would view favorably...)

Originally created by @jhsmith409 on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4356 ### What would you like to see? I realize this may be better handled by a more complete solution for RBAC across all of anythingLLM. I've read a number of feature requests looking for either the full RBAC solution or bits and pieces. So, far I have not seen anyone taking on the full task of RBAC. If I were to do that, I would look to using a database that supported that function for me which then becomes a huge project of changing the internal database of anythingLLM. This is complicated by RBAC being a paid feature in many databases. So short of full RBAC implementation, I, like others, am seeing limits where I can apply anythingLLM. I've seen Tim reject (and with good reason) other partial user permission enhancements that did not offer a full set of features. Despite this, my intention is to create a fork for User-based control of the RAG in a single Workspace and hope Tim will accept that back in. If not, I'll end out with a fork I have to maintain until full RBAC is implemented. Hoping with the right features, Tim would be willing to merge this back in before RBAC is implemented. (Fishing for comments from Tim as to what he would view favorably...)
yindo added the enhancementfeature request labels 2026-02-22 18:31:12 -05:00
yindo closed this issue 2026-02-22 18:31:12 -05:00
yindo commented 2026-02-22 18:31:12 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 8, 2025):

This older (but still relevant PR) #3799 is what you are likely looking for?

  • Doesnt break existing roles
  • Would allow admin to define basically a "schema" with custom roles and keys/perms
  • Would be installation specific, but not dependent on external services
  • Could be automated with an auth provider (like SSO) to generate or provision a custom roles per user.

However, as you would imagine - this is a whole overhaul of the current auth and is tricky, which is what is taking so long :(

@timothycarambat commented on GitHub (Sep 8, 2025): This older (but still relevant PR) #3799 is what you are likely looking for? - Doesnt break existing roles - Would allow admin to define basically a "schema" with custom roles and keys/perms - Would be installation specific, but not dependent on external services - _Could_ be automated with an auth provider (like SSO) to generate or provision a custom roles per user. However, as you would imagine - this is a whole overhaul of the current auth and is tricky, which is what is taking so long :(
yindo changed title from [FEAT]: User control of RAG database in a single workspace to [GH-ISSUE #4356] [FEAT]: User control of RAG database in a single workspace 2026-06-05 14:48:29 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2777
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?