docs: align agent create flow with 1.16.0 UI and finalize the data security notice (#887) (backport to release/1.16.0) - #889
Merged
Conversation
…curity notice (#887) * fix: match the agent create path to the roster's Create menu * docs: note agent DSL import and that skills and files stay behind * docs: finalize the data security notice and agent memory guidance - Replace the data security Warning on overview, build, and the node tab with the legal-final wording (en/zh/ja; zh header becomes 数据安全提示), each ending with an Enterprise contact-sales tail linking the per-language sales form. - Move the conversation-memory sentence from Publish to the overview's On Its Own section, where it describes the standalone chat app. - Note on the node tab that in a Chatflow the agent keeps no conversation-scoped memory (verified in a 1.16.0 deployment). - Reorder Publish (Logs and Monitoring before sharing) and tighten the DSL sharing sentence. * docs: require per-language sales-form links for Contact sales Enterprise Tips now link Contact sales to the HubSpot sales form for the page's language, never the pricing page, Enterprise docs, a webapp, or dify.ai. The three URLs live in the Enterprise Tip section; repointing the 19 legacy links is tracked separately. * docs: trim the re-add advice from the DSL import note * style: use an Info callout for the agent API note (cherry picked from commit 4259941)
dosubot
Bot
added
the
size:L
Contributor
There was a problem hiding this comment.
Pull request overview
This backport updates the New Agent documentation set for the release/1.16.0 docs to match the shipped 1.16.0 UI and the finalized “Data Security Notice” wording, including the per-language Contact Sales form links and the clarified memory behavior guidance.
Changes:
- Updates the Data Security Notice text (and sales-form links) across the New Agent docs and node docs in en/zh/ja.
- Aligns the agent creation flow with the 1.16.0 UI (Create menu), and documents DSL import/export limitations (skills/files excluded).
- Moves/clarifies memory guidance: standalone agents have per-conversation memory; Chatflow-invoked agents do not keep conversation-scoped memory.
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| zh/self-host/use-dify/nodes/agent.mdx | Updates security notice wording and adds Chatflow memory note for the New Agent node. |
| zh/self-host/use-dify/build/new-agent/overview.mdx | Updates security notice wording and adds standalone per-conversation memory guidance. |
| zh/self-host/use-dify/build/new-agent/build.mdx | Updates create-path UI steps, adds DSL import/export notes, and updates the security notice. |
| ja/self-host/use-dify/nodes/agent.mdx | Updates security notice wording and adds Chatflow memory note for the New Agent node. |
| ja/self-host/use-dify/build/new-agent/overview.mdx | Updates security notice wording and adds standalone per-conversation memory guidance. |
| ja/self-host/use-dify/build/new-agent/build.mdx | Updates create-path UI steps, adds DSL import/export notes, and updates the security notice. |
| en/self-host/use-dify/nodes/agent.mdx | Updates security notice wording/link and adds Chatflow memory note for the Agent node. |
| en/self-host/use-dify/build/new-agent/overview.mdx | Updates security notice wording/link and adds standalone per-conversation memory guidance. |
| en/self-host/use-dify/build/new-agent/build.mdx | Updates create-path UI steps, adds DSL import/export notes, and updates the security notice. |
| writing-guides/style-guide.md | Updates Enterprise Tip guidance to use per-language Contact Sales form links and documents the mapping. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| **Data Security Notice** | ||
|
|
||
| When exposing the same agent to multiple end users in Community Edition, Dify applies precautionary safeguards intended to reduce cross-conversation data access risks. However, CE relies on soft isolation rather than hard per-user or per-run filesystem isolation, and runs may share the same underlying container or base filesystem. | ||
| Community Edition uses file-access controls to limit access to agent and session files when the same agent is exposed to multiple end users. These controls reduce the risk of cross-conversation data access through the filesystem, but the Agent runtime is not intended to provide a hardened security boundary between mutually untrusted users or workloads. |
| **Data Security Notice** | ||
|
|
||
| When exposing the same agent to multiple end users in Community Edition, Dify applies precautionary safeguards intended to reduce cross-conversation data access risks. However, CE relies on soft isolation rather than hard per-user or per-run filesystem isolation, and runs may share the same underlying container or base filesystem. | ||
| Community Edition uses file-access controls to limit access to agent and session files when the same agent is exposed to multiple end users. These controls reduce the risk of cross-conversation data access through the filesystem, but the Agent runtime is not intended to provide a hardened security boundary between mutually untrusted users or workloads. |
| **Data Security Notice** | ||
|
|
||
| When exposing the same agent to multiple end users in Community Edition, Dify applies precautionary safeguards intended to reduce cross-conversation data access risks. However, CE relies on soft isolation rather than hard per-user or per-run filesystem isolation, and runs may share the same underlying container or base filesystem. | ||
| Community Edition uses file-access controls to limit access to agent and session files when the same agent is exposed to multiple end users. These controls reduce the risk of cross-conversation data access through the filesystem, but the Agent runtime is not intended to provide a hardened security boundary between mutually untrusted users or workloads. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
maintorelease/1.16.0: