Add Dashboard operation and restructure contents

Author: Meggielqk

en_US/dashboard/cluster_settings.md

@@ -3,6 +3,7 @@
 EMQX provides hot configuration capabilities, which can dynamically modify the configuration at runtime without restarting the EMQX node. The EMQX Dashboard provides a visual configuration page for the hot configuration function, allowing you to easily modify the configuration of EMQX. The following configuration items are currently provided:
 
 - MQTT Settings
+- Namespace
 - Listeners
 - Logging
 - Monitoring
@@ -44,6 +45,10 @@ You can configure settings for the following fields in the **Force Shutdown** ta
 - **Max Heap Size**: Specifies the maximum allowed heap size for the system. If the heap size surpasses this limit, the system will initiate a forced shutdown to maintain stability. The default value is `32 MB`.
 - **Max Mailbox Size**: Defines the maximum allowed length for the mailbox message queue. If the queue exceeds this length, a forced shutdown will be triggered to prevent system overload. The default value is `1000`.
 
+## Namespace
+
+The Namespace feature in EMQX provides logical isolation for different client groups within a single cluster. You can manage namespaces on the **Namespace **page. For more detailed guidance on how to manage and configure namespaces, refer to the [Namespace](../multi-tenancy/namespace.md).
+
 ## Listeners
 
 Click on **Management** -> **Listeners** in the left menu to enter the listeners page. This page displays a list of listeners by default. EMQX provides four common listeners:

en_US/multi-tenancy/namespace.md

@@ -33,35 +33,27 @@ For example, to use the client's username as the namespace identifier, you can u
 mqtt.client_attrs_init = [{expression = username, set_as_attr = tns}]
 ```
 
-## Manage Namespace
-
-Most of the namespace features are only configurable via the [REST API](../admin/api.md).
-
-::: tip
-
-Always check the corresponding Swagger API documentation for detailed and up-to-date request and response endpoint schemas. These are served by the Dashboard listeners at `/api-docs`.
-
-:::
-
-### Create a Namespace
+### Methods for Creating a Namespace
 
-Before applying namespace-specific configuration, the namespace must be explicitly created using the `POST /mt/ns/<namespace>` API. Replace `<namespace>` with the desired namespace ID. No request body is required.
+There are two methods for creating namespaces: explicit creation and automatic creation.
 
-### Configure Namespace
+1. **Explicit Namespace Creation**
+   You can manually create a namespace through the Dashboard or REST API. Explicitly created namespaces can be directly managed, edited, and deleted.
 
-After the namespace is created, it can be configured using the `PUT /mt/ns/<namespace>/config` API.
+   **Use Case**: This method is ideal when you need full control over which namespaces exist and wish to manage them individually.
 
-Use this endpoint to set rate limits, session limits, and other namespace-specific settings. For example configurations, see the [Quick Start](#configure-rate-limiter-per-namespace) section below.
+2. **Automatic Namespace Creation via EMQX Extracting `client_attrs.tns`**
+   When clients connect, EMQX can automatically create namespaces based on the client’s `client_attrs.tns` attribute. This method is usually used in scenarios where manual namespace creation is not necessary and is suitable for large-scale automated deployments.
 
-### Delete a Namespace
+   **Use Case**: This approach works best for environments where clients connect dynamically, and each tenant or client requires an automatically generated, independent namespace.
 
-To remove a namespace and its associated configuration, you can use the `DELETE /mt/ns/<namespace>` API.
+   ::: tip Note
 
-::: tip Note
+   Automatically created namespaces cannot be edited in the Dashboard. They are generated either through configuration files or automatically based on client metadata.
 
-Before deleting a namespace, ensure that all active clients associated with the namespace are properly disconnected. EMQX provides an API to bulk kick all sessions under a namespace, and this process should be triggered automatically when deleting a managed namespace.
+   :::
 
-:::
+With these two methods, you can choose the most appropriate way to create namespaces based on your needs. Explicit creation is ideal for environments requiring strict control, while automatic creation is suitable for dynamic environments with reduced manual intervention.
 
 ## Quick Start: Configure Rate Limiter per Namespace
 
@@ -87,13 +79,13 @@ For more details, refer to the [Rate Limit](../rate-limit/rate-limit.md) documen
 
 :::
 
-## Configuration Example
+### Example of Configuring a Namespace via REST API
 
-Suppose you want to configure some specific rate limits for clients in the `ns1` namespace. You also want to limit the maximum number of concurrent sessions allowed in this namespace.
+This example configures a namespace using the [REST API](../admin/api.md). Suppose you want to configure some specific rate limits for clients in the `ns1` namespace. You also want to limit the maximum number of concurrent sessions allowed in this namespace.
 
-### Create the Namespace
+#### Create the Namespace
 
-Before applying any configuration, ensure the namespace is explicitly managed:
+Before applying any configuration, ensure the namespace is explicitly created:
 
 ```bash
 # No request body is needed
@@ -102,11 +94,11 @@ POST /mt/ns/ns1
 
 ::: tip Important Notice
 
-If clients connect to a namespace before it is explicitly managed, they will not inherit configurations such as rate limiters applied later. To enforce new settings, those clients must be manually disconnected and reconnected.
+If clients connect to a namespace before it is explicitly created, they will not inherit configurations such as rate limiters applied later. To enforce new settings, those clients must be manually disconnected and reconnected.
 
 :::
 
-### Configure Rate Limits and Session Limits
+#### Configure Rate Limits and Session Limits
 
 Once the namespace is created, apply the configuration using:
 
@@ -148,7 +140,7 @@ PUT /mt/ns/ns1/config
 
 This configuration applies both client-specific and shared tenant-wide rate limits and sets a maximum of 100 sessions for the namespace.
 
-### Disable Namespace Rate Limiters
+#### Disable Namespace Rate Limiters
 
 If you want to remove rate limiting entirely, you can update the configuration again and set the limiter types to `"disabled"`:
 
@@ -166,3 +158,99 @@ PUT /mt/ns/ns1/config
   }
 }
 ```
+
+## Manage Namespace
+
+You can configure and manage namespaces through the Dashboard and REST API.
+
+### Manage Namespaces via Dashboard
+
+In the Dashboard, click **Manage** -> **Namespace** in the left menu. On the **Namespaces** page, you can view, create, edit, and delete namespaces, as well as manage clients connected to namespaces.
+
+By default, the namespace list only shows explicitly created namespaces. You can toggle the switch at the top left of the page to show both explicitly created namespaces and those automatically created by EMQX from the `client_attrs.tns` attribute.
+
+::: tip
+
+Automatically created namespaces cannot be edited in the Dashboard.
+
+:::
+
+#### Create a Namespace
+
+1. Click **Create** in the top right corner of the **Namespaces** page.
+
+2. In the **Create Namespace** dialog, complete the following configuration:
+
+   - **Namespace**: Enter the namespace name.
+
+   - **Max Sessions**: By default, this is set to `infinity` (unlimited). If enabled, you can set a specific number to limit the maximum number of sessions, preventing too many clients from occupying resources in a single namespace. When setting the max sessions, ensure it aligns with your cluster capacity to avoid rejected connections due to a low limit.
+
+   - **Tenant Limiter**: This configuration controls the traffic for all clients within the namespace. For instance, when multiple clients share the same infrastructure, tenant rate limits ensure fair bandwidth distribution. By default, this is disabled. If enabled, you can configure the following rate limits:
+
+     ::: tip
+
+     For more details on this configuration, refer to the tooltips in the Dashboard.
+
+     :::
+
+     - **Data Publish Rate**: Limits the bytes the current tenant can send to EMQX per second.
+     - **Data Publish Burst**: Allows additional bytes to be sent during bursts.
+     - **Messages Publish Rate**: Limits the maximum number of messages a tenant can send per second.
+     - **Messages Publish Burst**: Allows additional messages to be sent during bursts.
+
+   - **Client Limiter**: This configuration controls traffic for individual clients. Client rate limiters are exclusive to each client, meaning the rate limit for one client won’t affect others. By default, this is disabled. If enabled, you can configure the following rate limits:
+
+     ::: tip
+
+     For more details on this configuration, refer to the tooltips in the Dashboard.
+
+     :::
+
+     - **Data Publish Rate**: Limits the bytes a client can send to EMQX per second.
+     - **Data Publish Burst**: Allows additional bytes to be sent during bursts.
+     - **Messages Publish Rate**: Limits the maximum number of messages a client can send per second.
+     - **Messages Publish Burst**: Allows additional messages to be sent during bursts.
+
+3. After completing the configuration, click **Create**. The new namespace will appear in the list.
+
+#### Manage Namespaces
+
+To edit the settings for a specific namespace, click **Edit** in the **Actions** column for that namespace.
+
+To delete a namespace, click **Delete** in the **Actions** column. After confirming, the namespace will be permanently deleted.
+
+::: tip Note
+
+Before deleting a namespace, ensure that all active clients associated with the namespace are properly disconnected.
+
+:::
+
+To view clients connected to a specific namespace, click **Clients** in the **Actions** column. You can also choose to bulk disconnect clients.
+
+### Manage Namespaces via REST API
+
+::: tip
+
+Always check the corresponding Swagger API documentation for detailed and up-to-date request and response endpoint schemas. These are served by the Dashboard listeners at `/api-docs`.
+
+:::
+
+### Create a Namespace
+
+Before applying namespace-specific configuration, the namespace must be explicitly created using the `POST /mt/ns/<namespace>` API. Replace `<namespace>` with the desired namespace ID. No request body is required.
+
+### Configure Namespace
+
+After the namespace is created, it can be configured using the `PUT /mt/ns/<namespace>/config` API.
+
+Use this endpoint to set rate limits, session limits, and other namespace-specific settings. For example configurations, see the [Quick Start](#quick-start-configure-rate-limiter-per-namespace) section below.
+
+### Delete a Namespace
+
+To remove a namespace and its associated configuration, you can use the `DELETE /mt/ns/<namespace>` API.
+
+::: tip Note
+
+Before deleting a namespace, ensure that all active clients associated with the namespace are properly disconnected. EMQX provides an API to bulk kick all sessions under a namespace, and this process should be triggered automatically when deleting a managed namespace.
+
+:::

zh_CN/dashboard/cluster_settings.md

@@ -3,6 +3,7 @@
 EMQX 提供了热配置能力，可以在运行时动态修改配置，无需重启 EMQX 节点。EMQX Dashboard 针对热配置功能，提供了一个可视化配置页面。通过该页面，可以方便的修改 EMQX 的配置。目前提供了以下配置项：
 
 - MQTT 配置
+- 命名空间
 - 监听器
 - 日志
 - 监控
@@ -44,6 +45,10 @@ EMQX 提供了热配置能力，可以在运行时动态修改配置，无需重
 - **最大堆内存**：指定系统允许的最大堆内存大小。如果堆内存超出此限制，系统将启动强制关闭，以保持稳定性。默认为`32 MB`。
 - **最大邮箱大小**：定义邮箱消息队列的最大允许长度。如果队列长度超过此限制，系统将触发强制关闭以防止系统过载。默认为`1000`。
 
+## 命名空间
+
+EMQX 中的命名空间功能为单个集群内的不同客户端组提供逻辑隔离。您可以在**命名空间**页面管理命名空间。有关如何管理和配置命名空间的详细指导，参阅[命名空间](../multi-tenancy/namespace.md)。
+
 ## 监听器
 
 点击左侧菜单中的**管理** -> **监听器**进入监听器页面。该页面默认是一个监听器的列表页。EMQX 默认提供了四个常用的监听器：