Project Studios
Overview
The Project Studios section is used to manage interactive development workspaces (Jupyter Lab, VS Code, etc.) assigned to a specific Project within the DataFloem platform.
While the global Studio Module creates and manages development environments running in Kubernetes across the platform, those studios must first be explicitly assigned to a Project before they can be utilized for interactive development or linked with that Project's Code Flows.
When a new Project is created, its Studio list is empty. Users with appropriate permissions can assign required pre-registered studios to the project scope or unassign existing ones as needed.
Access Requirements
To access and manage this page, the user must have the required permissions for the specific Project and its associated Studios.
Users without the required permission cannot view this page and will receive an authorization error:
Access Denied
You don't have access to this resource.
Users with access can monitor their permission level via the
Access Status column (Granted)
for each assigned studio.
Managing Project Studios
This page displays all Studio workspaces currently assigned to the Project, with options to toggle between List and Grid/Card layout views.
From this page you can:
-
View all assigned Studios, their workspace types (
LaborVS Code), and access statuses. -
Search (
Filter...) and filter the assigned Studio list. - Toggle between list and grid views for optimal visibility.
- Assign existing global Studios to the project using the Assign Studio button.
-
Remove (unassign) Studios from the project scope using the action menu
(
...). -
Monitor system operational statuses (
Active/Inactive).
Studio Information Table
The table displays the following information for each assigned Studio:
| Field | Description |
|---|---|
| Access Status |
Indicates whether the project/user has been successfully granted
access to use this studio (e.g.,
Granted).
|
| Name |
Unique display name of the Studio workspace (e.g.,
Studio1).
|
| Type |
The development environment type (e.g.,
Lab for Jupyter Lab, or
VS Code).
|
| Update Date | Date and time when the studio assignment or configuration was last updated. |
| Status |
Operational system status of the Studio connector (e.g.,
Active).
|
| Actions (...) |
Action menu (...) allowing users to
perform project-level actions such as Unassign.
|
Key Features & Actions
Assign Studio
Clicking the Assign Studio button opens the studio assignment interface where you can select and link pre-configured global Studios to the current project.
Unassigning a Studio
Selecting Unassign from the action menu (...) removes the Studio from the current project scope. This action does not
delete the underlying Kubernetes workspace or global Studio configuration;
it only revokes its availability for the current project.
Notes
- Assigning a studio to a project links an existing global studio configuration to the project scope; it does not instantiate a new Kubernetes workspace.
- Unassigning a studio only removes it from the current Project's scope. It remains available in the global Studio Module for other projects.
-
Ensure that assigned studios have an operational
Status of
Activeto prevent connection errors during development workflows.