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 #4796] [FEAT]: Shared conversation mode for team workspaces #3016

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

Originally created by @romandidomizio on GitHub (Dec 18, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4796

What would you like to see?

Use Case

We need a "Team Mode" for workspaces where all users can see and continue
the same conversation history - creating a shared team memory/knowledge base.

Current Behavior

  • Multi-user mode: Chat history is isolated per user (by design)
  • Users in the same workspace cannot see each other's conversations

Requested Feature

Add a workspace-level setting: "Enable shared conversation history"

  • When enabled: All workspace members see the same conversation thread
  • When disabled: Current per-user isolation (default)

Business Value

  • Team collaboration with shared AI context
  • Reduces duplicate questions
  • Enables collective learning from AI interactions
Originally created by @romandidomizio on GitHub (Dec 18, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4796 ### What would you like to see? ## Use Case We need a "Team Mode" for workspaces where all users can see and continue the same conversation history - creating a shared team memory/knowledge base. ## Current Behavior - Multi-user mode: Chat history is isolated per user (by design) - Users in the same workspace cannot see each other's conversations ## Requested Feature Add a workspace-level setting: "Enable shared conversation history" - When enabled: All workspace members see the same conversation thread - When disabled: Current per-user isolation (default) ## Business Value - Team collaboration with shared AI context - Reduces duplicate questions - Enables collective learning from AI interactions
yindo added the enhancementfeature request labels 2026-02-22 18:32:16 -05:00
yindo closed this issue 2026-02-22 18:32:16 -05:00
yindo commented 2026-02-22 18:32:16 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 2, 2026):

This is something we wont support as a feature as it adds a ton of overhead complexity and also undoes the basic isolation a user would expect in a multi-user system. That being said, if you want to be able to share workspace and chats with anybody, you should likely use the "Password only" authentication mode.

This has its own drawbacks, but it would in effect have the same idea.

The only alternative is allowing users to share a conversation up to a specific point with another user (like a clone of the chat history). However, sub-users should not be allowed or even aware of others on the service ideally.

@timothycarambat commented on GitHub (Jan 2, 2026): This is something we wont support as a feature as it adds a ton of overhead complexity and also undoes the basic isolation a user would expect in a multi-user system. That being said, if you want to be able to share workspace and chats with anybody, you should likely use the "Password only" authentication mode. This has its own drawbacks, but it would in effect have the same idea. The only alternative is allowing users to share a conversation up to a specific point with another user (like a clone of the chat history). However, sub-users should not be allowed or even aware of others on the service ideally.
yindo changed title from [FEAT]: Shared conversation mode for team workspaces to [GH-ISSUE #4796] [FEAT]: Shared conversation mode for team workspaces 2026-06-05 14:49:50 -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#3016
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?