**Question: Conversation sharing and multi-user access in Dify chatflows**

[ally687]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I'm building a client intake workflow where multiple people from the same organization may need to participate in the same conversation at different times. For example:

1. The CEO starts a conversation with the chatflow, answers some questions, then says "Our controller will upload the financial documents later."
2. I send the controller the link to continue the conversation.

My questions:

1. Can the controller see the previous conversation history? If I share the URL of an existing conversation, will a new user see the messages that have already been exchanged, or will they start with a blank screen?

2. How do I share a conversation so someone else can continue it? Is there a specific URL format or sharing mechanism I should use?

3. What happens if two people access the same conversation simultaneously? Will their messages queue properly, or could this cause conflicts?

4. Does this behavior differ between the Dify Cloud version and self-hosted?

I'm using a chatflow with state management via conversation variables. I want to make sure the state persists correctly when different users continue the same engagement.

Thanks!

2. Additional context or comments

No response

[dosubot[bot]]

Here’s how conversation sharing and multi-user access work in Dify chatflows:

1. If you share a conversation URL, the recipient will only see the previous conversation history if they access it with the same user/session context as the original creator. If the user/session context doesn’t match, Dify will show a “Conversation Not Exists” error and the history won’t load. There’s no built-in way for a different user to pick up an existing conversation with full history unless you’re explicitly sharing the same user/session context (for example, by using a shared user ID or session) (source, source).

2. To share a conversation so someone else can continue it, you need to share the conversation URL that includes the correct conversation ID and user/session context. If you want true multi-user continuation, you’ll need to implement a shared user/session mechanism or manage the conversation history and state externally (for example, by storing and replaying the conversation context yourself) (source, source). Passing variables via URL (gzip + base64 encoded) is supported for workflow inputs, but this does not override the core access control for conversation history (source).

3. If two people access the same conversation simultaneously (with the same user/session context), Dify does not provide explicit locking or conflict resolution at the conversation/message level. Each user/task gets its own queue, and concurrency is managed per user. True cross-user concurrent access is not supported by default, so you may encounter race conditions or message order issues if you try to coordinate multiple users this way (source, source).

4. There are no documented or coded differences between Dify Cloud and self-hosted versions regarding conversation sharing, access control, or state persistence. Both use the same stateless architecture and client-side history management (source).

5. Conversation variables (state) are persisted per conversation and user/session context. If you want state to persist across different users, you’ll need to implement an external mechanism to synchronize or transfer state, as Dify does not natively support multi-user memory sharing in chatflows (source, source).

If you need true multi-user collaboration, consider using a shared user/session context or building a custom layer to manage and synchronize conversation history and state outside of Dify’s built-in mechanisms.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}