Creating and Managing a Workspace

The system will create a default workspace and assign the admin role to you after you create a DataArts Studio instance. can use the default workspace or create a new workspace.

A workspace in a DataArts Studio instance is the basic unit for member management and role and permission allocation. It provides all DataArts Studio functions. Workspaces are allocated by branch or subsidiary (such as the group, subsidiary, and department), business domain (such as the procurement, production, and sales), or implementation environment (such as the development, test, and production environment). There are no fixed rules.

Admins can manage user (member) permissions, resources, and compute engines in a workspace. To enable users to work together, admins can add users to a workspace and assign the preset roles of DataArts Studio (admin, developer, operator, and visitor) to the users. Users other than admins can access Management Center, DataArts Migration, and DataArts Factory only after they are added to a workspace and assigned relevant roles.

Constraints

  • There is no limit on the number of workspaces that can be created for a DataArts Studio instance. You can plan the quota as needed.

  • The storage of job logs and dirty data depends on the OBS service.

Prerequisites

You have created a DataArts Studio instance by referring to Creating a DataArts Studio Basic Package.

Background

  • The system will create a default workspace and assign the admin role to you after you create a DataArts Studio instance.

  • In a DataArts Studio instance created by a master account, if an IAM user of the account needs to create a workspace, the IAM user must be assigned the DARTS Administrator or Tenant Administrator policy. By default, the master account has all the permissions for a DataArts Studio instance created by a sub-user.

  • Users assigned the permissions of DARTS User can access a workspace only after they are added as members of the workspace.

Creating a Workspace

  1. Log in to the DataArts Studio console as user DARTS Administrator or Tenant Administrator. For details, see Accessing the DataArts Studio Instance Console.

  2. On the Workspaces page, click Create. In the displayed dialog box, set parameters based on Table 1.

    **Figure 1** Creating a workspace

    Figure 1 Creating a workspace

    Table 1 Parameters for creating a workspace

    Parameter

    Description

    Name

    Workspace names can contain only letters, numbers, underscores (_), and hyphens (-). They cannot exceed 32 characters. In a DataArts Studio instance, workspace names must be unique.

    Description

    A description of the workspace.

    Mode

    Workspace mode

    • Simple: This traditional mode is easy to use but does not allow you to strictly control the data development process and table permissions.

    • Enterprise: You can isolate the development environment from the production environment in the DataArts Factory and Management Center modules of DataArts Studio. This prevents developers' operations from affecting services in the production environment. For details about the enterprise mode, see DataArts Studio Enterprise Mode Overview.

    Enterprise Project

    Enterprise project associated with the default workspace of the DataArts Studio instance.

    This parameter is available only when an enterprise project has been created. If you want to connect the DataArts Studio instance to a cloud service (such as DWS, MRS, and RDS), ensure that the enterprise project of the DataArts Studio workspace is the same as that of the cloud service instance.

    • You can only create one DataArts Studio instance in an enterprise project.

    • If you want to enable communication between DataArts Studio and another cloud service, ensure that the enterprise project of DataArts Studio is the same as that of the cloud service.

    OBS Bucket for Job Logs

    The OBS bucket for storing logs of DataArts Studio data development jobs. To use the DataArts Factory module of DataArts Studio, workspace members must have the read and write permissions on the OBS bucket for storing job logs. Otherwise, the system cannot read or write job logs generated during data development.

    • Click Select. You can select a created OBS bucket. The selected OBS bucket is globally configured in the current workspace.

    • If this parameter is not set, job logs generated during data development are stored in the OBS bucket named dlf-log-{projectId} by default. {projectId} indicates the project ID, which can be obtained by referring to Obtaining a Project ID and Account ID.

    OBS Bucket for DLI Dirty Data

    The OBS bucket for storing dirty data generated during DLI SQL execution in DataArts Studio Data Development. To use DataArts Studio DataArts Factory to develop and execute DLI SQL statements, workspace members must have the read and write permissions on the OBS bucket where DLI dirty data is stored. Otherwise, the system cannot read or write the dirty data generated during DLI SQL execution.

    • Click Select. You can select a created OBS bucket. The selected OBS bucket is globally configured in the current workspace.

    • If this parameter is not set, dirty data generated during DLI SQL execution is stored in the OBS bucket named dlf-log-{projectId} by default.

  3. Click OK.

last updated: 2025-07-09 16:05 UTC - commit: 61336f3c2e25ce26cb038bce82678d028fe5d438