Skip to content

Workspace

1. Function Overview

1.1 Function Definition

Workspace is the core module for resource grouping management provided by the Console. It is positioned as a "logically isolated project-level management unit". Each Workspace is equivalent to an independent project space, enabling three-dimensional isolation management of resources, permissions, and bills. By creating multiple Workspaces, users can build non-interfering business units within the unified Console to meet the needs of refined management in complex scenarios.

1.2 Core Values

  • Resource Isolation: Establish logical boundaries to achieve physical - level isolation and storage of resources between different projects

  • Permission Hierarchy: Support for configuring independent permission policies for different Workspaces to ensure data security

  • Cost clarity: Bill statistics are performed according to the Workspace dimension to accurately locate the resource consumption of each project

  • Management Efficiency: Simplify the complexity of multi - project parallel operation through grouped management

2. Core Function Description

2.1 Resource Management System

2.1.1 Resource Ownership Rules

  • Create and Bind: All resources (including but not limited to MaaS, Search, AI EDU, etc.) will be assigned to a Workspace when they are created.

  • Isolation Mechanism: Resources are completely isolated between different Workspaces. Cross-space access or call is not allowed. Physical Separation of data is achieved from the underlying architecture.

2.1.2 Group Management Function

  • Support for creating/deleting Workspaces and custom naming

  • Support subsequent migration management of new and existing resources

2.2 Multi-dimensional isolation characteristics

2.2.1 Operation Interface Isolation

  • Independent Workspace management page, where the resource list, configuration items, and operation logs of each space are displayed independently

  • Support quick switching of workspace views. The current operation only takes effect on the selected Workspace

2.2.3 Billing Statistics System

  • Independent Billing Page: Each workspace has its own billing view, showing real-time resource usage details

  • Multi - dimensional statistical report: Support generating expense bills on a daily / monthly basis

  • Billing Export Function: Export the billing data of the specified Workspace in CSV/Excel format to meet the financial accounting requirements

3. Typical Usage Scenarios

3.1 Multi-project parallel management

It is suitable for enterprises that operate multiple independent projects at the same time. By creating a dedicated Workspace for each project, the following can be achieved:

  • Project resources are managed independently to avoid misoperation of cross-project resources

  • Team permissions are accurately divided, and different project groups can only access the resources of their own space

  • The project cost is accounted for separately, clearly showing the input-output ratio of each project

3.2 Isolation of Development and Testing

In the management of development - test - production environment, it is realized through Workspace:

  • The Development Environment is completely isolated from the production environment to ensure the security of online data

  • The test resources are configured independently to avoid the impact of test operations on the formal environment

  • Each environment cost is counted separately to optimize resource input allocation

3.3 Sub-account hierarchical management

For the management scenario of multiple subsidiaries of group enterprises:

  • Create a dedicated Workspace for each subsidiary to implement account permission classification

  • The subsidiary's bills are independently counted, which is convenient for the group's financial summary and accounting

  • Resource calls are strictly isolated, meeting the requirements of enterprise internal control management

4. Operation Guide

4.1 Create a Workspace

  1. Visit the workspace settings page , click the plus sign to add a new workspace

Support authorizing sub - accounts to access specified workspaces. Only authorized sub - accounts can access resources in the workspace

alt text

4.2 Resource Creation and Ownership

1. Create

Resources created from the current workspace page belong to that workspace

2. Transfer of resources

Refer to the following figure to transfer resources from the source workspace to the target workspace (only the list of workspaces you currently have permissions to is shown)

alt text

4.3 Authorization of workspace

Visit this page https://console.cloudsway.net/tools/roleManage to authorize the workspace account menu for the specified user, and you can view and manage the addition, deletion and modification of the workspace

alt text

4.4 Resource Group Upgrade and Migration Mechanism

For historical stock resource group users, the system provides a smooth transition plan to support the independent planning of the Workspace grouping system:

4.4.1 Initial migration rules

  • Default grouping process: All historical resource groups will be automatically assigned to the system default Default Workspace. The original resource ownership relationship remains unchanged, and the current business operation is not affected.

4.4.2 Self-service migration operation process

  1. Create a Workspace with the same name

  2. Enter the "Workspace Management" page, click [New Workspace], and the name can be exactly the same as the original resource group name (supporting a mixture of Chinese and English, case-sensitive)

  3. Configure the permission policy for this Workspace

  4. Migrate resources

  5. In the resource list of the Default Workspace, select the original resource group associated resources to be migrated for migration (support screening by "original resource group name")

  6. The system will complete the resource migration within 5-10 minutes, during which the resources can be accessed normally

4.4.3 Precautions

  • Permission reset mechanism: Resources migrated to the new Workspace will inherit the permission policy of the target Workspace, and the user/role Right of access needs to be reconfigured

  • Bill cutting node: The resource migration completion time is used as the bill statistics demarcation point. The consumption before this is counted into the Default Workspace, and the consumption after this is counted into the target Workspace

(Hint: If your business does not require sub - grouping, you can directly use the Default Workspace for management. The system will continuously ensure the resource isolation and bill statistics functions of this space)