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 #587] [FEAT]: Privacy Scoping: Documents, Workspaces and Chats #339

New Issue
Closed
opened 2026-02-22 18:19:01 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:19:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @sumitsodhi88 on GitHub (Jan 13, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/587

What would you like to see?

So we have several managers with several teams working under them. The data for each team is sensitive in nature and should not be shared outside of the circle. But as the other teams have the access to all the documents uploaded, this brings a risk to our work and may cause leakage. Please make a provision to hide uploaded documents to the other managers.

And why are the all workspaces be available to all maangers. Let the admin decide whom to give access to the workspace except the ones created by the managers themselves.

Another issue is that the managers should not be allowed to see chat history and only administrator should have that right. This feature is required to implement in large organisations where we require several managers with separate workspaces.

Eesentially three features are required:

  1. Document privacy.
  2. Workspace privacy.
  3. Chat privacy.

Screenshot 2024-01-13 233023

Originally created by @sumitsodhi88 on GitHub (Jan 13, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/587 ### What would you like to see? So we have several managers with several teams working under them. The data for each team is sensitive in nature and should not be shared outside of the circle. But as the other teams have the access to all the documents uploaded, this brings a risk to our work and may cause leakage. Please make a provision to hide uploaded documents to the other managers. And why are the all workspaces be available to all maangers. Let the admin decide whom to give access to the workspace except the ones created by the managers themselves. Another issue is that the managers should not be allowed to see chat history and only administrator should have that right. This feature is required to implement in large organisations where we require several managers with separate workspaces. Eesentially three features are required: 1. Document privacy. 2. Workspace privacy. 3. Chat privacy. ![Screenshot 2024-01-13 233023](https://github.com/Mintplex-Labs/anything-llm/assets/149290101/9fbd086a-48f7-468c-b872-a162ffa40761)
yindo added the enhancementfeature request labels 2026-02-22 18:19:01 -05:00
yindo closed this issue 2026-02-22 18:19:01 -05:00
yindo commented 2026-02-22 18:19:01 -05:00
Author
Owner
Copy Link
Copy Source

@sumitsodhi88 commented on GitHub (Mar 13, 2024):

@timothycarambat this is essential for large scale implementation. please prioritize this as I am waiting for this feature before pushing to my organisation.

@sumitsodhi88 commented on GitHub (Mar 13, 2024): @timothycarambat this is essential for large scale implementation. please prioritize this as I am waiting for this feature before pushing to my organisation.
yindo commented 2026-02-22 18:19:01 -05:00
Author
Owner
Copy Link
Copy Source

@rpaGuyai commented on GitHub (Jun 10, 2024):

@timothycarambat This is very important feature, we are unable to roll out at enterprise level due to this, there should be super user / workspace level manager/admin access, current manager role doesn't really make sense as the manager can see all the work spaces.

@rpaGuyai commented on GitHub (Jun 10, 2024): @timothycarambat This is very important feature, we are unable to roll out at enterprise level due to this, there should be super user / workspace level manager/admin access, current manager role doesn't really make sense as the manager can see all the work spaces.
yindo commented 2026-02-22 18:19:01 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 28, 2024):

Moving to https://github.com/Mintplex-Labs/anything-llm/issues/1787

@timothycarambat commented on GitHub (Jun 28, 2024): Moving to https://github.com/Mintplex-Labs/anything-llm/issues/1787
yindo changed title from [FEAT]: Privacy Scoping: Documents, Workspaces and Chats to [GH-ISSUE #587] [FEAT]: Privacy Scoping: Documents, Workspaces and Chats 2026-06-05 14:34:47 -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#339
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?