RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
Go agent-harnessagent-native-databaseagentic-aiagentic-retrievalagentic-searchaiai-agentscontext-enginecontext-engineeringcontext-managementharness-engineeringknowledge-compilationragretrieval-augmented-generationretrieval-harnesssearch-harness
docs:Restructure the Team documentation and align sharing configuration across Dataset, Agent, and Memory. (#21922)
YanZhang91f3c41091ac
diff --git a/docs/administrator/management/admin_ui/check_system_status.md b/docs/administrator/management/admin_ui/check_system_status.mdindex 57d978bbb0..a91250cab2 100644--- a/docs/administrator/management/admin_ui/check_system_status.md+++ b/docs/administrator/management/admin_ui/check_system_status.md@@ -40,15 +40,11 @@ On the **Services** page, administrators can view the service `Name`, `Service tThe MySQL dialog displays the health-check record, not a database process list. Use your deployment's database administration tools if you need to inspect SQL sessions or processes.---+To view **Extra information**, hover over the service row and click the sliders icon in **Actions**. The dialog displays the elapsed value and message included in the status record. Click **Close** to return to the list. A failed dependency check can place its error text in the message field.---+If a service's status is not `alive`, record its name, service type, host, port, and message before troubleshooting the corresponding dependency or process.diff --git a/docs/guides/agent/embed_workflows_into_web_pages.md b/docs/guides/agent/embed_workflows_into_web_pages.mdindex c82950b7e2..c29a1c4145 100644--- a/docs/guides/agent/embed_workflows_into_web_pages.md+++ b/docs/guides/agent/embed_workflows_into_web_pages.md@@ -19,11 +19,15 @@ Steps:1. On the Agent page, click the target Agent to open its editing page.2. Click **Management > Embed into webpage** in the upper right corner of the canvas to open the embedding settings.- + 3. In **Embed Setup**, choose **Fullscreen chat (traditional iframe)** or **Floating widget (Intercom-style)**.4. Set **Language**, **User ID**, and display options as needed. Enable **Published** to use the published version of the Agent.++ +5. For a floating widget, use **Widget Customization** to adjust its title, text, and colors. Click **Save widget settings** to save the settings.-6. Copy **Embed code** into your webpage. Use **Open in new tab** to preview the result.-+ ++6. Copy **Embed code** into your webpage. Use **Open in new tab** to preview the result.diff --git a/docs/guides/agent/ingestion_pipeline/configure_parser_component.md b/docs/guides/agent/ingestion_pipeline/configure_parser_component.mdindex 17dd92baab..a2a2828289 100644--- a/docs/guides/agent/ingestion_pipeline/configure_parser_component.md+++ b/docs/guides/agent/ingestion_pipeline/configure_parser_component.md@@ -34,7 +34,7 @@ This switch is separate from **OCR** under Image: OCR recognizes text, while visThe **Parser** dropdown includes **DeepDOC**, **Naive**, **Docling**, **OpenDataLoader**, **TCADP Parser**, and **MonkeyOCRv2**, followed by available configured models grouped by provider. Choose a parser appropriate for your deployment and document layout, and validate its results on a sample file. **Naive** provides simple text extraction for text-based PDFs.-+Some selections expose additional controls:diff --git a/docs/guides/agent/ingestion_pipeline/create_ingestion_pipeline.md b/docs/guides/agent/ingestion_pipeline/create_ingestion_pipeline.mdindex ea8a64d361..e53279f760 100644--- a/docs/guides/agent/ingestion_pipeline/create_ingestion_pipeline.md+++ b/docs/guides/agent/ingestion_pipeline/create_ingestion_pipeline.md@@ -70,3 +70,13 @@ Publishing another version does not switch the version already selected by a DatTo export, open an editable pipeline and choose **Management > Export**. The browser downloads the current canvas configuration as a JSON file.To import, select **Agent > Ingestion pipeline**, choose **Import JSON file** from the creation menu, enter **Name**, upload the pipeline JSON under **DSL**, and click **Save**. Open the imported card and check models, compilation template groups, and other referenced resources. These resources are not transferred by importing JSON. Save the draft, publish a version, and validate it in a test Dataset before use.++## Sharing Scope++1. Open the pipeline under **Agent > Ingestion pipeline**.+2. Click **Management > Settings** in the upper-right corner.+3. In the **Edit** dialog, find **Permissions**.+4. Select **me** to keep it private, or **Team** to share it with your team.+5. Click **Save**.++See [Team resource permissions](../../team/resource_sharing/resource_sharing_and_permissions.md#member-permissions) for member access after sharing.diff --git a/docs/guides/agent/understand_workflow_canvas.md b/docs/guides/agent/understand_workflow_canvas.mdindex 957a862ce2..c4c8c3c24e 100644--- a/docs/guides/agent/understand_workflow_canvas.md+++ b/docs/guides/agent/understand_workflow_canvas.md@@ -43,7 +43,7 @@ Operation Steps:6. After selection, the variable will be automatically inserted into the input box.7. Save component configuration and run the Agent to verify data transmission.-+## Canvas ToolbarThe buttons in the upper-right corner let you save, test, publish, and manage the workflow.@@ -83,3 +83,13 @@ Connections define component execution order. Sequential components run along aClick any canvas component to open the right-side configuration panel, which displays fields, input variables, output variables and execution settings. Recommended workflow: confirm which variable the component reads → configure processing logic → verify downstream nodes reference correct outputs.For slow workflows, see [Improve Agent Response Time](./best_practices/accelerate_agent_question_answering.md).++## Sharing Scope++1. Open the workflow under **Agent > Workflow**.+2. Click **Management > Settings** in the upper-right corner.+3. In the **Edit** dialog, find **Permissions**.+4. Select **me** to keep it private, or **Team** to share it with your team.+5. Click **Save**.++See [Team resource permissions](../team/resource_sharing/resource_sharing_and_permissions.md#member-permissions) for what members can do after sharing.diff --git a/docs/guides/chat/chat_configuration.md b/docs/guides/chat/chat_configuration.mdindex 1dd60aade3..862dc0e1bb 100644--- a/docs/guides/chat/chat_configuration.md+++ b/docs/guides/chat/chat_configuration.md@@ -128,3 +128,9 @@ The mode selector is beside the message box. Before sending a question, open itSelecting a mode chooses the flow for the question. Configure that flow in the corresponding **Naive** or **Agentic** settings group, save the Chat, and test both modes with representative questions. See [Using Chat conversations](./using_chat_sessions.md) for the message-box controls.++## Use a Shared Dataset++In **Chat setting > Datasets**, select the shared Dataset, then click **Save**. Select the model for generating answers under **Chat setting > Model**.++See [Team resource permissions](../team/resource_sharing/resource_sharing_and_permissions.md#member-permissions) for access to shared resources and how model use differs between Chat and Dataset parsing.diff --git a/docs/guides/dataset/configuration.md b/docs/guides/dataset/configuration.mdindex 4b3a14279c..7d7f089187 100644--- a/docs/guides/dataset/configuration.md+++ b/docs/guides/dataset/configuration.md@@ -360,3 +360,14 @@ The **Data source** area is used to associate the current dataset with data sourClick **Link data source** and select the data source to associate from existing data sources. After association, the current dataset can use the data provided by that data source. This area is only used to establish and manage the association between the dataset and data sources. It does not provide data source creation or connection configuration.> Tip: To add a new data source, or configure data source connection information, synchronization methods, and other settings, see [**Data source**](../../guides/data_source/overview_and_page_management.md). After adding the data source, return to the dataset configuration page to associate it.++## Sharing Scope++1. Open **Dataset** and select the Dataset.+2. Open **Configuration > Basic** and find **Permissions**.+3. Select **Only me** to keep it private, or **Team** to share it with your team.+4. Click **Save**.++++See [Team resource permissions](../team/resource_sharing/resource_sharing_and_permissions.md#member-permissions) for what members can do after sharing.diff --git a/docs/guides/knowledge_compilation/built_in_templates_and_dedicated_configuration.md b/docs/guides/knowledge_compilation/built_in_templates_and_dedicated_configuration.mdindex 8d98b34608..d7025f9521 100644--- a/docs/guides/knowledge_compilation/built_in_templates_and_dedicated_configuration.md+++ b/docs/guides/knowledge_compilation/built_in_templates_and_dedicated_configuration.md@@ -135,7 +135,6 @@ The extracted claims include supporting evidence from the source chunks and areLeave this field empty to use the built-in claim extraction rules. Customize it only when you need domain-specific claim extraction requirements.-### Maximum TokensSets the maximum length for node summary generation. A larger value can preserve more summary information and is suitable for more complex documents. A smaller value can generate more concise summaries and is suitable for quickly viewing a document overview.@@ -158,7 +157,7 @@ This allows the final retrieval chunks to follow the semantic boundaries identifOnly one Tree template in the same template group can enable this option.-+## PageIndex@@ -553,8 +552,7 @@ The system provides the following blueprints:| Blueprint | Specifies the template for Wiki page generation. || Instruction | Supplements page generation rules, such as chapter structure, content format, and display requirements. |--+After a blueprint is selected, the system generates Wiki content according to the preset page structure and rules of the corresponding blueprint. When Custom is selected, you can customize page generation requirements through Instruction, such as chapter structure, content format, and display method.@@ -564,8 +562,6 @@ After configuring a blueprint, you can preview the Wiki page structure correspon### Configuration Recommendations-For structurally complex content such as enterprise knowledge bases and product documentation, it is recommended to enable Plan.-Entity types should be adjusted based on the business domain to avoid configuring too many irrelevant entities.Relationship types should remain clear and avoid defining relationships with duplicate meanings.diff --git a/docs/guides/memory/configure_memory.md b/docs/guides/memory/configure_memory.mdindex a21e54c31e..b32296c14b 100644--- a/docs/guides/memory/configure_memory.md+++ b/docs/guides/memory/configure_memory.md@@ -12,7 +12,7 @@ sidebar_custom_props: {The configuration page is used to maintain a memory's basic information, model configuration, capacity configuration, and advanced settings. After making changes, click **Confirm** to save them, or click **Cancel** to discard unsaved content.-On the memory page, click the target memory **> Configurations** to view and update its settings.+On the memory page, click the target memory **> Configuration** to view and update its settings.### Basic Information@@ -43,9 +43,18 @@ Memory size is used to limit the capacity that the memory can occupy. The valueAdvanced settings are used to control the memory's visibility scope, storage method, and extraction effect. If there are no special requirements, you can keep the default configuration.-- **Permissions**: Select **Only me** or **Team**. **Only me** means that only the current user can see the memory. **Team** means that team members can see and use the memory.+- **Permission**: Select **Only me** to keep the memory private, or **Team** to share it with your team. Click **Confirm** to save. See [Sharing Scope](#sharing-scope) for the full steps.- **Storage type**: Currently, **Table (`table`)** can be selected. It is suitable for general messages, field queries, and regular retrieval.- **Forgetting policy**: Currently, **First in, first out (FIFO)** can be selected. When the capacity reaches the upper limit, the system preferentially cleans up content written earlier.- **Temperature**: The value range is `0-1`. It is used to control the randomness of memory extraction. A lower value makes the extraction result more stable, while a higher value makes the expression more divergent.- **System prompt**: Used to define the role, output format, and structure constraints for memory extraction. Adjust it only when you need to unify the extraction format or strengthen extraction rules.- **User prompt**: Used to supplement user-side extraction requirements. If there are no special requirements, it can be left empty.++## Sharing Scope++1. Open **Memory** and select the memory.+2. Click **Configuration** and expand **Advanced settings**.+3. Under **Permission**, select **Only me** to keep it private, or **Team** to share it with your team.+4. Click **Confirm**.++See [Team resource permissions](../team/resource_sharing/resource_sharing_and_permissions.md#member-permissions) for what members can do after sharing.diff --git a/docs/guides/memory/connect_to_an_agent.md b/docs/guides/memory/connect_to_an_agent.mdindex 8e966ee43f..4068219677 100644--- a/docs/guides/memory/connect_to_an_agent.md+++ b/docs/guides/memory/connect_to_an_agent.md@@ -20,8 +20,7 @@ A memory must be connected to an Agent before historical messages can be written4. Select the target memory. If historical records need to be distinguished by user, configure the user ID.5. Save the Agent and run a test. After it runs, return to the memory's **Messages** page to check whether new messages have been generated.--+### Let an Agent Retrieve from Memory@@ -32,5 +31,4 @@ A memory must be connected to an Agent before historical messages can be written5. Connect the retrieval result to a subsequent large language model or answer component, so that the Agent can use the retrieved historical context.6. Save and run a test, and check whether the answer correctly references historical memories.--+diff --git a/docs/guides/team/_category_.json b/docs/guides/team/_category_.jsonindex c74611f48a..610fbb3289 100644--- a/docs/guides/team/_category_.json+++ b/docs/guides/team/_category_.json@@ -2,8 +2,8 @@"label": "Team","position": 8,"link": {- "type": "generated-index",- "description": "Team-specific guides."+ "type": "doc",+ "id": "guides/team/index"},"customProps": {"categoryIcon": "LucideUsers"diff --git a/docs/guides/team/index.md b/docs/guides/team/index.mdnew file mode 100644index 0000000000..78966ab656--- /dev/null+++ b/docs/guides/team/index.md@@ -0,0 +1,24 @@+---+sidebar_position: 1+sidebar_custom_props: {+ categoryIcon: LucideUserCog+}+sidebar_label: Team Overview+title: Team Overview+---++# Team Overview++Each account has its own workspace. Workspace owners can invite members, and account holders can join other teams to access shared resources.++Use the following links to access common tasks:++| Task | Guide |+| --- | --- |+| Invite team members | [Invite Members](team_management/manage_team_members.md#invite-members) |+| Accept a team invitation | [Accept or Decline an Invitation](team_management/join_and_leave_teams.md#accept-or-decline-an-invitation) |+| Configure resource sharing | [Resource Sharing and Permissions](resource_sharing/resource_sharing_and_permissions.md) |+| Review member permissions | [Team Member Permissions](resource_sharing/resource_sharing_and_permissions.md#member-permissions) |+| Review shared resource access conditions | [Resource Sharing and Permissions](resource_sharing/resource_sharing_and_permissions.md#access-rules) |++Joining a team gives you access only to resources the owner has shared with **Team**; private resources remain unavailable.diff --git a/docs/guides/team/permission_system_overview/_category_.json b/docs/guides/team/permission_system_overview/_category_.jsondeleted file mode 100644index 55acc4ddaf..0000000000--- a/docs/guides/team/permission_system_overview/_category_.json+++ /dev/null@@ -1,11 +0,0 @@-{- "label": "Permission System Overview",- "position": 1,- "link": {- "type": "generated-index",- "description": "Permission system overview."- },- "customProps": {- "categoryIcon": "LucideUserCog"- }-}diff --git a/docs/guides/team/permission_system_overview/index.md b/docs/guides/team/permission_system_overview/index.mddeleted file mode 100644index 13fddf0a0a..0000000000--- a/docs/guides/team/permission_system_overview/index.md+++ /dev/null@@ -1,14 +0,0 @@-----sidebar_position: 1-slug: /permission_system_overview-sidebar_custom_props: {- categoryIcon: LucideUserCog-}-sidebar_label: Overview-title: Overview-----# Permission System Overview--RAGFlow manages team collaboration and resource permissions through three layers: team membership, resource sharing scope, and resource operation permissions.--The **Team and Permissions** section describes how users enter the team page, view members in the current workspace, invite or remove members, accept or decline invitations, leave joined teams, and configure visible scopes for shared resources such as knowledge bases, Agents, chats, Search applications, and memories.diff --git a/docs/guides/team/permission_system_overview/permission_effective_rules.md b/docs/guides/team/permission_system_overview/permission_effective_rules.mddeleted file mode 100644index 0fa4c689bd..0000000000--- a/docs/guides/team/permission_system_overview/permission_effective_rules.md+++ /dev/null@@ -1,19 +0,0 @@-----sidebar_position: 5-sidebar_label: Permission Effective Rules-title: Permission Effective Rules------# Permission Effective Rules--When a user performs an operation on a resource, RAGFlow evaluates permissions in the following order:--1. Whether the user has formally joined the team that owns the resource.-2. Whether the resource sharing scope allows team access.-3. Whether the user has knowledge base-level, resource-level, or collaborator-level **Read**, **Write**, or **Manage** permission.-4. Whether the target document has additional document-level **Read**, **Write**, or **Manage** permission requirements.-5. Whether the current operation is allowed by the permission table for that resource type.--The resource owner always has all permissions. If a resource is set to **Only me**, only the owner can access it. If a resource is set to **Team**, only team members who meet the permission conditions can access it.--If finer-grained permissions exist, such as document-level permissions in a knowledge base, those permissions continue to apply on top of resource access permission.diff --git a/docs/guides/team/permission_system_overview/resource_operation_permissions.md b/docs/guides/team/permission_system_overview/resource_operation_permissions.mddeleted file mode 100644index 318a4a67f8..0000000000--- a/docs/guides/team/permission_system_overview/resource_operation_permissions.md+++ /dev/null@@ -1,21 +0,0 @@-----sidebar_position: 4-sidebar_label: Resource Operation Permissions-title: Resource Operation Permissions------# Resource Operation Permissions--Resource operation permissions define what a user can do after the resource becomes visible to the user.--Operation permissions can apply to the following resource types:--- Knowledge bases and knowledge base documents.-- Chat applications.-- Agents.-- MCP servers.-- Memories and memory messages.-- Search applications.-- Model providers, model instances, and default model configuration.--Different resources use different permission levels. Common permission levels include **Read permission**, **Write permission**, and **Manage permission**. The resource owner always has the highest permission on the resource.diff --git a/docs/guides/team/permission_system_overview/resource_sharing_scope.md b/docs/guides/team/permission_system_overview/resource_sharing_scope.mddeleted file mode 100644index fd130a1334..0000000000--- a/docs/guides/team/permission_system_overview/resource_sharing_scope.md+++ /dev/null@@ -1,13 +0,0 @@-----sidebar_position: 3-sidebar_label: Resource Sharing Scope-title: Resource Sharing Scope------# Resource Sharing Scope--Sharing scope controls the visible scope of a resource, that is, which users can access the current resource.--In the open-source edition, supported resources can usually be set to **Only me** or **Team**.--A resource set to **Team** is not necessarily visible to every user in every case. The system still checks whether the user belongs to the resource owner's team, whether the resource supports team sharing, and whether the user's operation is allowed by the corresponding permission rules.diff --git a/docs/guides/team/permission_system_overview/team_and_resource_permissions.md b/docs/guides/team/permission_system_overview/team_and_resource_permissions.mddeleted file mode 100644index c8ffbd19b2..0000000000--- a/docs/guides/team/permission_system_overview/team_and_resource_permissions.md+++ /dev/null@@ -1,20 +0,0 @@-----sidebar_position: 2-sidebar_label: Team and Resource Permissions-title: Team and Resource Permissions------# Team and Resource Permissions--Team membership and resource permissions are separate concepts.--A user may be a member of a team, but that does not mean the user can access every resource in the team. A resource must also be shared with the team or explicitly authorized to the user through collaborator permissions.--For common resource sharing scopes:--| Sharing scope | Description |-| --- | --- |-| Only me / me | Only the owner can access the resource. |-| Team / team | Users who have joined the team may access the resource if the resource-level permission rules allow it. |--When a team owner invites a user, the relationship is first created with the `invite` role. After the invited user accepts the invitation, the role changes to `normal`.diff --git a/docs/guides/team/permission_system_overview/team_member_management.md b/docs/guides/team/permission_system_overview/team_member_management.mddeleted file mode 100644index aef372f110..0000000000--- a/docs/guides/team/permission_system_overview/team_member_management.md+++ /dev/null@@ -1,25 +0,0 @@-----sidebar_position: 1-sidebar_label: Team Member Management-title: Team Member Management------# Team Member Management--Each user has a personal workspace. The team page of that workspace is displayed with the current user's nickname and **workspace** as its title.--The team page contains two main areas:--- **Team members**: Members in the current workspace.-- **Joined teams**: Other workspaces that the current user has joined or has been invited to join.--RAGFlow uses the `user_tenant` relationship to record team membership. Common role values include:--| Role | Description |-| --- | --- |-| owner | The owner of the workspace. The owner can invite members and remove members. |-| normal | A user who has accepted an invitation and joined the workspace. |-| invite | A user who has been invited but has not accepted the invitation. |-| admin | A backend role value used by the system. |--The team role is different from the Enterprise role management feature. Team roles define whether a user belongs to a workspace and what team-level actions the user can perform. Enterprise roles define action permissions for administrative resources.diff --git a/docs/guides/team/resource_sharing/_category_.json b/docs/guides/team/resource_sharing/_category_.jsonnew file mode 100644index 0000000000..ab3ec4fcd1--- /dev/null+++ b/docs/guides/team/resource_sharing/_category_.json@@ -0,0 +1,11 @@+{+ "label": "Resource Sharing",+ "position": 2,+ "link": {+ "type": "generated-index",+ "description": "Guides on resource sharing, member permissions, and using shared resources with your team."+ },+ "customProps": {+ "categoryIcon": "LucideShare2"+ }+}diff --git a/docs/guides/team/resource_sharing/resource_sharing_and_permissions.md b/docs/guides/team/resource_sharing/resource_sharing_and_permissions.mdnew file mode 100644index 0000000000..23fcee30e0--- /dev/null+++ b/docs/guides/team/resource_sharing/resource_sharing_and_permissions.md@@ -0,0 +1,83 @@+---+sidebar_position: 1+sidebar_label: Resource Sharing and Permissions+title: Resource Sharing and Permissions+---++# Resource Sharing and Permissions++This section describes sharing scope, access conditions, and member permissions for shared resources.++## Sharing Scope++Resources that support sharing have two scopes:++| Scope | Who can access the resource |+| --- | --- |+| Only me | Only the owner. |+| Team | The owner and members who have joined the owner's team. |++Workflow and ingestion pipeline settings display **me** for **Only me**; it is the same private scope.++### Find the Sharing Setting++| Resource | How to configure sharing | Team usage guide |+| --- | --- | --- |+| Dataset | [Dataset sharing settings](../../dataset/configuration.md#sharing-scope) | [Use Datasets with Your Team](use_datasets_with_your_team.md) |+| Workflow | [Workflow sharing settings](../../agent/understand_workflow_canvas.md#sharing-scope) | [Workflow team usage](use_agent_with_your_team.md#workflow-member-permissions) |+| Ingestion pipeline | [Ingestion pipeline sharing settings](../../agent/ingestion_pipeline/create_ingestion_pipeline.md#sharing-scope) | [Ingestion pipeline team usage](use_agent_with_your_team.md#ingestion-pipeline-member-permissions) |+| Memory | [Memory sharing settings](../../memory/configure_memory.md#sharing-scope) | [Use Memories with Your Team](use_memories_with_your_team.md) |++## Access Rules++Members can access a resource when both conditions are met:++- They have accepted the invitation to the resource owner's team.+- The owner has set the resource's sharing scope to **Team** and saved the setting.++An invitation awaiting acceptance does not grant access. Private resources remain available only to their owner.++### When Access Ends++Members lose team-based access when the owner makes the resource private, they leave the team, or the owner removes them.++Document creators retain permission to read, update, and delete their own documents, even after team-based access ends. This does not grant access to the entire Dataset or documents created by other members.++Joining another team does not share resources from a member's own workspace with that team.++## Member Permissions++The following tables summarize member permissions for shared resources. Available actions vary by resource type.++### Dataset Permissions++| Action | Workspace owner | Joined team member |+| --- | --- | --- |+| View files and use the Dataset for retrieval | Yes | Yes |+| Upload and parse files | Yes | Yes |+| Edit or delete files in the Dataset | Yes | Yes |+| Update Dataset configuration, including parsing settings | Yes | Yes |+| Change the Dataset's sharing scope | Yes | No |+| Delete the Dataset itself | Yes | No |++Deleting files does not delete the Dataset itself; only the workspace owner can delete the Dataset.++### Other Resource Permissions++The following table lists the permissions of members who have joined the resource owner's team.++| Shared resource | View | Edit | Run or use | Delete resource | Change sharing |+| --- | --- | --- | --- | --- | --- |+| Workflow | Yes | Yes | Yes | Owner only | Owner only |+| Ingestion pipeline | Yes | Yes | Use a published version in a Dataset | Owner only | Owner only |+| Memory | Yes | Yes | Yes | Yes | Owner only |++For Memory message controls and the effect of deletion, see [Use Memories with Your Team](use_memories_with_your_team.md).++Chat has no team sharing setting. Members can create their own Chat using a shared Dataset; the owner's Chat and conversations remain private.++For model use, see [Dataset parsing](use_datasets_with_your_team.md#parse-files-as-a-team-member), [Chat with a shared Dataset](use_datasets_with_your_team.md#use-a-shared-dataset-in-chat), [shared Workflows](use_agent_with_your_team.md#models-used-by-shared-workflows), or [shared Memories](use_memories_with_your_team.md).++#### Why Can I See a Button but Not Complete the Action?++Some owner-only controls remain visible to members. For example, a member may see **Delete** for a shared workflow but cannot delete it. Ask the owner to perform these actions.diff --git a/docs/guides/team/resource_sharing/use_agent_with_your_team.md b/docs/guides/team/resource_sharing/use_agent_with_your_team.mdnew file mode 100644index 0000000000..ccaa951798--- /dev/null+++ b/docs/guides/team/resource_sharing/use_agent_with_your_team.md@@ -0,0 +1,36 @@+---+sidebar_position: 3+sidebar_label: Use Agent with Your Team+title: Use Agent with Your Team+---++# Use Agent with Your Team++Share workflows and ingestion pipelines from the **Agent** page to enable team collaboration.++## Workflow Member Permissions++After joining the team, members can view, edit, and run shared workflows under **Agent > Workflow**. All members edit the same draft.++See [Workflow canvas: Sharing Scope](../../agent/understand_workflow_canvas.md#sharing-scope) for the configuration steps.++Only the workflow owner can delete the workflow or change its sharing scope. Sharing a workflow does not automatically share private Datasets or memories referenced by its components; configure those resources separately.++### Models Used by Shared Workflows++Shared workflows use the models selected in their components and the model provider configuration in the workflow's workspace, rather than the member's personal defaults. If a model is unavailable, ask the owner to check its configuration.++### Drafts and Published Versions++Members edit the same draft. Canvas changes are autosaved; **Save draft** also saves the current draft explicitly. Neither action updates a published version.++- **Run** tests the draft.+- **Publish** creates a published version. Saving a draft does not update a published version.++A selected published version remains in use until another version is selected. Start a new conversation to test updated replies; existing conversations may retain the earlier workflow configuration.++## Ingestion Pipeline Member Permissions++Find shared pipelines under **Agent > Ingestion pipeline**. Members can view and edit them, and use a published version to process Dataset files. Draft edits do not update the version already selected by a Dataset. Only the owner can delete a pipeline or change its sharing scope.++See [Ingestion pipeline sharing settings](../../agent/ingestion_pipeline/create_ingestion_pipeline.md#sharing-scope) for the configuration steps.diff --git a/docs/guides/team/resource_sharing/use_datasets_with_your_team.md b/docs/guides/team/resource_sharing/use_datasets_with_your_team.mdnew file mode 100644index 0000000000..46ef9e0627--- /dev/null+++ b/docs/guides/team/resource_sharing/use_datasets_with_your_team.md@@ -0,0 +1,27 @@+---+sidebar_position: 2+sidebar_label: Use Datasets with Your Team+title: Use Datasets with Your Team+---++# Use Datasets with Your Team++Share a Dataset to allow team members to manage and use the same documents.++Joined members can find the shared Dataset in their **Dataset** list. If it does not appear, see [Why Can't an Invited User See Shared Resources?](../team_management/join_and_leave_teams.md#why-cant-an-invited-user-see-shared-resources).++When the owner changes the scope back to **Only me**, other team members lose access.++Members can view content, upload, parse, edit, or delete files, and update Dataset configuration. These changes affect everyone using the Dataset. Only the workspace owner can change its sharing scope or delete the Dataset itself.++See [Dataset configuration: Sharing Scope](../../dataset/configuration.md#sharing-scope) for the configuration steps.++## Parse Files as a Team Member++For parsing steps, see [Start Parsing](../../dataset/files_dataset_document_management.md#start-parsing).++Parsing uses the Dataset or pipeline's configured models from the Dataset owner's workspace, even when a member starts it. Members do not need to configure these models in their own accounts. If a model is unavailable, contact the owner to verify its configuration.++## Use a Shared Dataset in Chat++A shared Dataset does not automatically share a Chat that uses it. A member can create their own Chat and select the shared Dataset; that Chat uses its own configured chat model. See [Chat configuration: Datasets](../../chat/chat_configuration.md#datasets) to select it.diff --git a/docs/guides/team/resource_sharing/use_memories_with_your_team.md b/docs/guides/team/resource_sharing/use_memories_with_your_team.mdnew file mode 100644index 0000000000..df460fa78c--- /dev/null+++ b/docs/guides/team/resource_sharing/use_memories_with_your_team.md@@ -0,0 +1,23 @@+---+sidebar_position: 4+sidebar_label: Use Memories with Your Team+title: Use Memories with Your Team+---++# Use Memories with Your Team++Share a Memory to allow team members to use and manage its configuration and messages.++Joined members can find the shared memory in their **Memory** list and use it in workflows. They can view messages, edit memory configuration, enable or disable messages, and use **Forget**.++See [Memory configuration: Sharing Scope](../../memory/configure_memory.md#sharing-scope) for the configuration steps.++## Forget Messages or Delete a Memory++Use **Forget** to stop a message from appearing in retrieval results without immediately deleting its record.++Members can also delete the shared Memory. Once deleted, it is no longer available to any team member. Only the owner can change its sharing scope.++## Models Used by Shared Memories++Memory extraction and retrieval use the LLM and embedding model configured in the Memory owner's workspace, rather than members' default models. See [Configure Memory](../../memory/configure_memory.md) for model settings.diff --git a/docs/guides/team/sharing_scope_configuration/_category_.json b/docs/guides/team/sharing_scope_configuration/_category_.jsondeleted file mode 100644index 414bdaf510..0000000000--- a/docs/guides/team/sharing_scope_configuration/_category_.json+++ /dev/null@@ -1,11 +0,0 @@-{- "label": "Sharing Scope Configuration",- "position": 3,- "link": {- "type": "generated-index",- "description": "Sharing scope configuration."- },- "customProps": {- "categoryIcon": "LucideShare2"- }-}diff --git a/docs/guides/team/sharing_scope_configuration/index.md b/docs/guides/team/sharing_scope_configuration/index.mddeleted file mode 100644index 9fef108fcf..0000000000--- a/docs/guides/team/sharing_scope_configuration/index.md+++ /dev/null@@ -1,16 +0,0 @@-----sidebar_position: 3-slug: /sharing_scope_configuration-sidebar_custom_props: {- categoryIcon: LucideShare2-}-sidebar_label: Overview-title: Overview-----# Sharing Scope Configuration--Configure the visible scope of resources in RAGFlow.-------Sharing scope controls which users can access the current resource. Resources that support team sharing, such as knowledge bases, Agents, chats, Search applications, and memories, can be configured with a sharing scope.diff --git a/docs/guides/team/sharing_scope_configuration/open_source_edition_sharing_scope_configuration.md b/docs/guides/team/sharing_scope_configuration/open_source_edition_sharing_scope_configuration.mddeleted file mode 100644index 2a92402bdf..0000000000--- a/docs/guides/team/sharing_scope_configuration/open_source_edition_sharing_scope_configuration.md+++ /dev/null@@ -1,16 +0,0 @@-----sidebar_position: 1-sidebar_label: Open-Source Edition Sharing Scope Configuration-title: Open-Source Edition Sharing Scope Configuration------# Open-Source Edition Sharing Scope Configuration--In the open-source edition, the sharing scope is configured through the **Permissions** field on the resource configuration page. Select one of the following options based on your business needs:--- **Only me**: Only the knowledge base owner can access the knowledge base.-- **Team**: The knowledge base can be shared within the team.--Resources are not shared automatically. To make a resource available to other users, explicitly configure its sharing scope or permissions.--diff --git a/docs/guides/team/sharing_scope_configuration/share_agents.md b/docs/guides/team/sharing_scope_configuration/share_agents.mddeleted file mode 100644index 44a18f5c97..0000000000--- a/docs/guides/team/sharing_scope_configuration/share_agents.md+++ /dev/null@@ -1,16 +0,0 @@-----sidebar_position: 7-sidebar_label: Share Agents-title: Share Agents------# Share Agents--To share an Agent:--1. Open the intended Agent in its editing canvas.-2. Click **Management** **>** **Settings** to open the **Agent settings** dialog.-3. Change **Permissions** from **Only me** to **Team**.-4. Click **Save** to apply your changes.--After this configuration is saved, team members can see the shared Agent.diff --git a/docs/guides/team/sharing_scope_configuration/share_knowledge_bases.md b/docs/guides/team/sharing_scope_configuration/share_knowledge_bases.mddeleted file mode 100644index d232f090a6..0000000000--- a/docs/guides/team/sharing_scope_configuration/share_knowledge_bases.md+++ /dev/null@@ -1,11 +0,0 @@-----sidebar_position: 5-sidebar_label: Share Knowledge Bases-title: Share Knowledge Bases------# Share Knowledge Bases--Share a knowledge base by changing its **Permissions** from **Only me** to **Team**.--Team members can upload and parse files in shared knowledge bases.diff --git a/docs/guides/team/sharing_scope_configuration/share_memories.md b/docs/guides/team/sharing_scope_configuration/share_memories.mddeleted file mode 100644index f38a7eb72a..0000000000--- a/docs/guides/team/sharing_scope_configuration/share_memories.md+++ /dev/null@@ -1,16 +0,0 @@-----sidebar_position: 9-sidebar_label: Share Memories-title: Share Memories------# Share Memories--To share a memory:--1. Navigate to the **Memory** page and open the intended memory.-2. Click **Configurations**.-3. Change **Permissions** from **Only me** to **Team**.-4. Click **Save** to apply your changes.--After this configuration is saved, team members can see the shared memory.diff --git a/docs/guides/team/team_management/_category_.json b/docs/guides/team/team_management/_category_.jsonindex 158039c9fa..3d7214a92f 100644--- a/docs/guides/team/team_management/_category_.json+++ b/docs/guides/team/team_management/_category_.json@@ -1,11 +1,11 @@{"label": "Team Management",- "position": 2,+ "position": 1,"link": {"type": "generated-index",- "description": "Team management."+ "description": "Guides on managing team members and joining or leaving teams."},"customProps": {- "categoryIcon": "LucideLogOut"+ "categoryIcon": "LucideUserCog"}}diff --git a/docs/guides/team/team_management/accept_or_decline_an_invitation.md b/docs/guides/team/team_management/accept_or_decline_an_invitation.mddeleted file mode 100644index 5f06aba2f1..0000000000--- a/docs/guides/team/team_management/accept_or_decline_an_invitation.md+++ /dev/null@@ -1,20 +0,0 @@-----sidebar_position: 6-sidebar_label: Accept or Decline an Invitation-title: Accept or Decline an Invitation------# Accept or Decline an Invitation--When another team owner invites you to join a team, you can process the invitation on the **Team** page.--If the membership role is `invite`, the **Joined teams** list displays **Agree** and **Refuse** operations.--- Click **Agree** to accept the invitation. The system changes the relationship role from `invite` to `normal`.-- Click **Refuse** to decline the invitation. The system deletes the invitation relationship.--Only an invitation relationship can be accepted. After accepting an invitation, you can access team-shared resources in that workspace when those resources also satisfy their sharing scope and operation permission rules.----diff --git a/docs/guides/team/team_management/enter_the_team_page.md b/docs/guides/team/team_management/enter_the_team_page.mddeleted file mode 100644index acdc65ad7a..0000000000--- a/docs/guides/team/team_management/enter_the_team_page.md+++ /dev/null@@ -1,13 +0,0 @@-----sidebar_position: 1-sidebar_label: Enter the Team Page-title: Enter the Team Page------# Enter the Team Page--Click your avatar in the upper-right corner of the page, then select **Team** in the left-side panel to access the **Team** page.--The page title is displayed as the current user's nickname plus **workspace**. On this page, you can view members in the current workspace and teams that the current user has joined.--diff --git a/docs/guides/team/team_management/faq.md b/docs/guides/team/team_management/faq.mddeleted file mode 100644index 4bf5504c9a..0000000000--- a/docs/guides/team/team_management/faq.md+++ /dev/null@@ -1,32 +0,0 @@-----sidebar_position: 11-sidebar_label: FAQ-title: FAQ------# FAQ--### Why Does Inviting a Member Fail?--Common causes include:--- The email address does not belong to an existing RAGFlow user.-- The user has already joined the team.-- The user has already been invited.-- The current user is not the team owner.--### Why Can't an Invited User See Team Resources?--The invited user must first click **Agree** to join the team. The target resource must also be set to **Team** or otherwise authorized to the user.--### Why Can a Team Member Only See Some Knowledge Bases After Joining a Team?--Only knowledge bases whose permissions allow team access are visible to joined team members.--### Why Can't a Team Member Delete a Shared Knowledge Base?--Deleting a shared knowledge base generally requires the current user to be the creator of the knowledge base. Team sharing grants access and use permissions, but it does not automatically grant delete permission.--### Are Team Roles the Same as Enterprise Roles?--No. Team roles describe membership in a workspace. Enterprise roles describe administrative resource action permissions.diff --git a/docs/guides/team/team_management/index.md b/docs/guides/team/team_management/index.mddeleted file mode 100644index e3c8461698..0000000000--- a/docs/guides/team/team_management/index.md+++ /dev/null@@ -1,24 +0,0 @@-----sidebar_position: 2-slug: /team_management-sidebar_custom_props: {- categoryIcon: LucideLogOut-}-sidebar_label: Overview-title: Overview-----# Team Management--Manage team members, team invitations, and joined teams.-------By default, each RAGFlow user is assigned a single team named after the user's name. RAGFlow allows you to invite RAGFlow users to your team. Your team members can help you:--- Upload documents to your shared datasets.-- Parse documents in your shared datasets.-- Use your shared Agents.--:::tip NOTE-- Team members cannot invite users to your team. Only the team owner can invite users or remove members.-:::diff --git a/docs/guides/team/team_management/invite_members.md b/docs/guides/team/team_management/invite_members.mddeleted file mode 100644index afc65f9867..0000000000--- a/docs/guides/team/team_management/invite_members.md+++ /dev/null@@ -1,24 +0,0 @@-----sidebar_position: 3-sidebar_label: Invite Members-title: Invite Members------# Invite Members--The team owner can invite RAGFlow users to join the team.--To invite a member:--1. Open the **Team** page.-2. In the **Team members** area, click **Invite**.-3. Enter the email address of the user to invite.-4. Click **OK**.--The email address must belong to an existing RAGFlow user. If the email address does not match any user, the system returns a user-not-found error. If the user has already joined the team or has already been invited, the system rejects the duplicate invitation.--After the invitation is created, the membership record is stored with the `invite` role. The invited user must accept the invitation before becoming a normal team member.----diff --git a/docs/guides/team/team_management/join_and_leave_teams.md b/docs/guides/team/team_management/join_and_leave_teams.mdnew file mode 100644index 0000000000..935828468e--- /dev/null+++ b/docs/guides/team/team_management/join_and_leave_teams.md@@ -0,0 +1,75 @@+---+sidebar_position: 2+sidebar_label: Join and Leave Teams+title: Join and Leave Teams+---++# Join and Leave Teams++Use **User settings > Team** to view joined teams, respond to invitations, or leave a team.++## View Joined Teams++Scroll to **Joined teams**. This list includes your own workspace, teams you have joined, and invitations awaiting your response.++++| Field | Description |+| --- | --- |+| Name | The team owner's nickname. |+| Date | The last update time for the team owner's account, not the date you joined the team. |+| Email | The team owner's email address. |+| Action | **Accept** and **Decline** for a pending invitation, or a leave-team icon for a team you have joined. Your own workspace has no leave action. |++Use this list's search box to search by the owner's nickname or email address. Click the sort button beside **Date** to change the order.++## Accept or Decline an Invitation++When someone invites you to their team, you can respond from your own account:++1. Find the invitation in **Joined teams**. The **Name** and **Email** columns identify the team owner.++ ++2. Choose **Accept** to join the team, or **Decline** to decline.++++After you accept, the invitation actions are replaced by a leave-team icon. Find resources shared with **Team** in the corresponding Dataset, Agent, or Memory list. See [Team usage guides](../resource_sharing/resource_sharing_and_permissions.md#find-the-sharing-setting). Private resources remain unavailable.++If you decline, the invitation is removed from the active list and you do not join the team. The owner can invite you again later if needed.++## Leave a Team++You can leave a team you have joined. You cannot leave your own workspace.++1. In **Joined teams**, find the team you want to leave.+2. Click the leave-team icon in **Action**.++ ++3. Check the confirmation message, then click **Delete** to leave. Choose **Cancel** to stay in the team.++Leaving removes the team from your joined list and ends your access to resources shared only with that team. It does not delete your account or your own workspace's resources.++To join again later, ask the owner to send you a new invitation.++## Common Questions++### Why Can't an Invited User See Shared Resources?++Confirm that the invitation has been accepted under **Joined teams**, then ask the owner to verify that the resource is set to **Team** and saved. Refresh the resource list. If access was previously available, confirm that the membership is still active. See [Resource Sharing and Permissions](../resource_sharing/resource_sharing_and_permissions.md#access-rules).++### Why Can I Only See Some Datasets After Joining a Team?++Only Datasets shared with your team appear. See [Resource Sharing and Permissions](../resource_sharing/resource_sharing_and_permissions.md) for who can access each scope.++### Why Does My Own Workspace Appear in Joined Teams?++The list includes your own workspace as well as other teams and pending invitations. Your own workspace has no leave action.++### Does Leaving a Team Delete My Account or Files?++No. Leaving ends your access to that team's shared resources. Your account and your own workspace's resources are kept.++To invite people to your own team or remove members, see [Manage Team Members](manage_team_members.md). For shared resource actions, see [Team Member Permissions](../resource_sharing/resource_sharing_and_permissions.md#member-permissions).diff --git a/docs/guides/team/team_management/leave_a_joined_team.md b/docs/guides/team/team_management/leave_a_joined_team.mddeleted file mode 100644index 46effb991c..0000000000--- a/docs/guides/team/team_management/leave_a_joined_team.md+++ /dev/null@@ -1,20 +0,0 @@-----sidebar_position: 7-sidebar_label: Leave a Joined Team-title: Leave a Joined Team------# Leave a Joined Team--A user with the `normal` role can leave a joined team if the team is not the user's own workspace.--To leave a joined team:--1. Open the **Team** page.-2. Find the target team in the **Joined teams** list.-3. Click the leave action.-4. Confirm the operation.--After leaving a team, the team no longer appears as a joined team. The user can no longer access resources that are only shared within that team. The user's own workspace does not provide a leave operation.--diff --git a/docs/guides/team/team_management/manage_team_members.md b/docs/guides/team/team_management/manage_team_members.mdnew file mode 100644index 0000000000..76d7d2730b--- /dev/null+++ b/docs/guides/team/team_management/manage_team_members.md@@ -0,0 +1,78 @@+---+sidebar_position: 1+sidebar_label: Manage Team Members+title: Manage Team Members+---++# Manage Team Members++This section describes how to view, invite, and remove members of your workspace. Only the workspace owner can invite or remove members.++## Open the Team Page++Click your avatar in the upper-right corner, open **User settings**, then select **Team** in the left sidebar.++++Each account has its own workspace. The page title shows your nickname followed by **workspace**.++The page contains two lists:++- **Team members** shows people you have invited to your workspace and those who have joined. Your own account is not listed as a member.+- **Joined teams** shows your own workspace, other teams you have joined, and invitations awaiting your response. Your own workspace has no leave action.++Joining another team does not switch **Team members** to that team's member list. To respond to another owner's invitation or leave their team, see [Join and Leave Teams](join_and_leave_teams.md).++## View Members++In **Team members**, review the people you have invited and those who have joined.++++| Field | Description |+| --- | --- |+| Name | The member's nickname. |+| Date | The last update time for the member's account, not the date they were invited or joined. |+| Email | The member's email address. |+| State | **Invite** means the invitation is awaiting a response. **Member** means the person has joined. |+| Action | The delete icon opens a confirmation to remove the member or cancel a pending invitation. |++Use the search box beside **Invite member** to search by nickname or email address. Click the sort button beside **Date** to change the order.++To view invitations from other owners or teams you have joined, see [View Joined Teams](join_and_leave_teams.md#view-joined-teams).++## Invite Members++Invite another registered RAGFlow user to collaborate on resources you share with your team.++1. In **Team members**, click **Invite member**.++ ++2. In the **Add** dialog, enter the user's email address.+3. Click **Ok**.++++The invited person appears with the **Invite** state until they accept. The recipient must [accept the invitation](join_and_leave_teams.md#accept-or-decline-an-invitation) from their own account. The state then changes to **Member**.++To share resources with your members, see [Resource Sharing and Permissions](../resource_sharing/resource_sharing_and_permissions.md).++### If the Invitation Fails++Check that the email belongs to a registered account and that the person is not already a member or awaiting an invitation response.++## Remove Members or Cancel Invitations++As the workspace owner, you can remove a member or cancel an invitation that has not yet been accepted.++1. Find the person in **Team members** and check their email address.+2. Click the delete icon in **Action**.++ ++3. In **Delete member**, click **Delete** to confirm, or **Cancel** to keep the person in the list.++Removing a member ends their access to resources shared only with your team. It does not delete their account or their personal resources. You can invite them again later if needed.++Your own account is not listed as a removable member of your workspace.diff --git a/docs/guides/team/team_management/remove_members.md b/docs/guides/team/team_management/remove_members.mddeleted file mode 100644index 8eea7644d4..0000000000--- a/docs/guides/team/team_management/remove_members.md+++ /dev/null@@ -1,20 +0,0 @@-----sidebar_position: 4-sidebar_label: Remove Members-title: Remove Members------# Remove Members--The team owner can remove members from the team.--To remove a member:--1. Open the **Team** page.-2. Find the member in the **Team members** list.-3. Click the delete action in the **Action** column.-4. Confirm the operation.--The workspace owner cannot be removed from the workspace. Removing a member does not delete the member's personal resources, but it affects the member's access to resources that are shared only within the team.--diff --git a/docs/guides/team/team_management/resource_sharing_from_the_team_perspective.md b/docs/guides/team/team_management/resource_sharing_from_the_team_perspective.mddeleted file mode 100644index 73b2a6b6f8..0000000000--- a/docs/guides/team/team_management/resource_sharing_from_the_team_perspective.md+++ /dev/null@@ -1,22 +0,0 @@-----sidebar_position: 9-sidebar_label: Resource Sharing from the Team Perspective-title: Resource Sharing from the Team Perspective------# Resource Sharing from the Team Perspective--Joining a team does not automatically grant access to all resources in that team. The resource itself must be shared with the team or authorized to the user.--For knowledge bases, the **Permissions** field can be set to **Only me** or **Team**. The default value is **Only me**. When the value is changed to **Team**, joined team members can see and use the knowledge base according to permission rules.--Knowledge base access follows these rules:--- If the current user belongs to the owner tenant, access is allowed.-- If the knowledge base permission is **Only me**, non-owners cannot access it.-- If the knowledge base permission is **Team** and the user belongs to the tenant, access is allowed.-- Deleting a knowledge base is stricter and generally requires the current user to be the creator.--Agent sharing also uses **Only me** and **Team**. The permission field is located in the Agent settings dialog. The default value is **Only me**.--Memory sharing is configured in the memory's advanced settings. **Only me** maps to `me`, and **Team** maps to `team`. The backend also defines an `all` value, but the UI exposes **Only me** and **Team**.diff --git a/docs/guides/team/team_management/view_current_workspace_members.md b/docs/guides/team/team_management/view_current_workspace_members.mddeleted file mode 100644index 0dbecba4ad..0000000000--- a/docs/guides/team/team_management/view_current_workspace_members.md+++ /dev/null@@ -1,25 +0,0 @@-----sidebar_position: 2-sidebar_label: View Current Workspace Members-title: View Current Workspace Members------# View Current Workspace Members--The **Team members** list displays members in the current workspace. The owner is not included in the ordinary member list returned by the backend member query.--The list contains the following fields:--| Field | Description |-| --- | --- |-| Name | The member's nickname. |-| Update date | The time when the membership record was last updated. |-| Email | The member's email address. |-| Status | The member's team relationship status. `normal` is displayed as **Member**, `invite` is displayed as **Invite**, and `owner` is displayed as **Owner**. |-| Action | Operations available for the current member, such as removing a member when permitted. |--You can search members by nickname or email address, and sort members by **Update date**.--Only the workspace owner can query and manage the full member list for the workspace.--diff --git a/docs/guides/team/team_management/view_joined_teams.md b/docs/guides/team/team_management/view_joined_teams.mddeleted file mode 100644index 5a8faa6d0f..0000000000--- a/docs/guides/team/team_management/view_joined_teams.md+++ /dev/null@@ -1,22 +0,0 @@-----sidebar_position: 5-sidebar_label: View Joined Teams-title: View Joined Teams------# View Joined Teams--The **Joined teams** list displays other workspaces that the current user has joined or has been invited to join.--The list contains the following fields:--| Field | Description |-| --- | --- |-| Name | The workspace owner's nickname. |-| Update date | The time when the membership record was last updated. |-| Email | The workspace owner's email address. |-| Action | Operations available for the joined team, such as accepting, declining, or leaving. |--You can search joined teams by the owner nickname or email address, and sort joined teams by **Update date**.--diff --git a/docs/release_notes.md b/docs/release_notes.mdindex d26cac8031..00999eb219 100644--- a/docs/release_notes.md+++ b/docs/release_notes.md@@ -1298,7 +1298,7 @@ Ensure that you [upgrade **both** your code **and** Docker image to this release#### Added documents- [Configurations](https://ragflow.io/docs/dev/configurations)-- [Manage team members](./guides/team/team_management/index.md)+- [Manage team members](guides/team/team_management/manage_team_members.md)- Run health check on RAGFlow's dependencies## v0.13.0