Studio Module - Users

Overview

The Studio Module is responsible for managing Studio environments within the system.

A Studio is an interactive development workspace that runs in a Kubernetes environment and is created for a specific Code Flow. Each Studio is associated with a single Code Flow and is intended to be used exclusively within that workflow.

A Studio provides users with a Jupyter Notebook environment where they can develop Python code, execute notebook cells interactively, inspect results in real time, and perform data analysis or development tasks. Once development is complete, the notebook can be saved as a file within the DataFlow platform and utilized by the associated Code Flow.

The Users page of the Studio Module allows administrators to manage user permissions for the Studio module.

By default, the page displays only users who already have at least one permission assigned for the Studio module. Users are displayed in a paginated list.

When Edit Mode is enabled, all users in the system are displayed, regardless of whether they currently have any permissions for the Studio module. Administrators can then assign, update, or remove Studio module permissions.

Prerequisites

Before managing Studio module user permissions, ensure that:

• You have administrator privileges.
• Users have already been created.
• At least one Studio has been configured in the system.

Viewing Users

When the page is opened:

• Users are displayed in a paginated table.
• Only users with at least one permission in the Studio module are shown.
• Each row displays the user's current Studio module permissions.

Edit Mode

Administrators can enable Edit Mode to modify user permissions.

When Edit Mode is enabled:

• All users in the system are displayed.
• Studio module permissions become editable.
• Permission changes are stored locally until they are saved.
• No changes are applied immediately.

Permission Assignment

Permissions can be assigned or removed directly from the user's row.

Selecting or deselecting a permission immediately updates the local state.

Changes remain pending until the administrator clicks Save.

Access Requirements

To access this page, the user must have the ACL permission for the Studios module.

The ACL permission allows users to manage authorization settings for the Studios module. Users without this permission cannot access this page unless they have administrator privileges.

Users without the required permission cannot view this page and will receive the following authorization error:

Access Denied

You don't have access to this resource.

Available Permissions

The following permissions are available within the Studio module.

Saving Changes

After permission changes have been made:

1. Review the pending changes.
2. Click Save.
3. Only modified permissions are sent to the server.
4. Once the request succeeds, the new permissions become effective.

Reset Changes

Clicking Reset discards all unsaved modifications.

The permission list is restored to its last saved state.

No requests are sent to the server when Reset is used.

Validation

The system validates all permission changes before saving.

Permission updates are persisted only after a successful save operation.

Permission Dependencies

Having the ACL permission in the Studio module alone is not sufficient to manage user permissions.

To manage users within the Studio module, the administrator must also have at least the GET permission in the Users Module.

Without the Users Module GET permission:

• Users cannot be retrieved.
• Studio module user permissions cannot be managed.
• The operation results in an authorization error.

This dependency exists because Studio module user management requires access to user information provided by the Users module.

Notes

• Permission changes are stored locally until Save is clicked.
• Reset discards all unsaved changes.
• Only modified permissions are submitted to the server.
• The user list is displayed using pagination for better performance.

Related Documentation

• Studios
• Users