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

[GH-ISSUE #4240] [FEAT]: Allow workspaces to inherit embedded documents #2696

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

Originally created by @terencemcdevitt-argondigital on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4240

What would you like to see?

We want to be able to allow some of our workspaces to "inherit" the embedded docs of other workspaces.

Consider this scenario - we're working with an enterprise client who has a set of global documents (either global to the company or global to a large project). We may have multiple workspaces for that client where those documents need to be embedded such that they'll be used for RAG on all related projects. For example, a corporate glossary of terms or rules/guidelines.

In the current AnythingLLM implementation, we'd need to manually embed each of those documents into each of the related projects. If any of those documents ever get updated, someone would need to know to update each workspace accordingly.

Ideally, we'd have a single place to put those documents and then indicate which projects should "inherit" those documents. Of course uploading into the "shared" set of documents would automatically update the vector databases for any of the workspaces that inherit.

Originally created by @terencemcdevitt-argondigital on GitHub (Aug 4, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4240 ### What would you like to see? We want to be able to allow some of our workspaces to "inherit" the embedded docs of other workspaces. Consider this scenario - we're working with an enterprise client who has a set of global documents (either global to the company or global to a large project). We may have multiple workspaces for that client where those documents need to be embedded such that they'll be used for RAG on all related projects. For example, a corporate glossary of terms or rules/guidelines. In the current AnythingLLM implementation, we'd need to manually embed each of those documents into each of the related projects. If any of those documents ever get updated, someone would need to know to update each workspace accordingly. Ideally, we'd have a single place to put those documents and then indicate which projects should "inherit" those documents. Of course uploading into the "shared" set of documents would automatically update the vector databases for any of the workspaces that inherit.
yindo added the enhancementfeature request labels 2026-02-22 18:30:50 -05:00
yindo closed this issue 2026-02-22 18:30:50 -05:00
yindo commented 2026-02-22 18:30:50 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Aug 4, 2025):

If you upload a document to any workspace, it is cached so upserts into subsequent workspaces should be near instant since it re-uses the embeddings again. If the file is watchable this would enable a document that is updated to sync, embed, and push that change to every associated workspace.

The idea of a "shared" workspace is interesting, albeit a bit complex I think for people to wrap their heads around given we have always had a workspace isolation approach.

@timothycarambat commented on GitHub (Aug 4, 2025): If you upload a document to any workspace, it is cached so upserts into subsequent workspaces should be near instant since it re-uses the embeddings again. If the file is [_watchable_](https://docs.anythingllm.com/beta-preview/active-features/live-document-sync) this would enable a document that is updated to sync, embed, and push that change to every associated workspace. The idea of a "shared" workspace is interesting, albeit a bit complex I think for people to wrap their heads around given we have always had a workspace isolation approach.
yindo changed title from [FEAT]: Allow workspaces to inherit embedded documents to [GH-ISSUE #4240] [FEAT]: Allow workspaces to inherit embedded documents 2026-06-05 14:48:01 -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#2696
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?