Sandbox Management
Once you create a Sandbox, you gain access to a full suite of environment management tools.
Runtime
Image loading...
Runtime tab is the hub for all the vital Sandbox information for monitoring their runtime.
Logs
The Logs tab provides real-time access to Sandbox system logs, showing details about service initialization and status updates.
Boot & Install Commands
The Boot & Install CMDs tab contains detailed Sandbox execution logs, showing progress of package installation, system updates, network tests and service configuration. This section lets you monitor the detailed process of environment initialization in real time.
Terminal
The Terminal tab provides direct access to the Sandbox command line.
Image loading...
Filesystem
The Filesystem tab provides access to files within Sandbox.
Image loading...
Activity
The Activity tab displays the history of pipeline runs in the Sandbox, including information about their status, date, and branch.
Image loading...
Snapshots
The Snapshots tab allows you to create and manage existing Sandbox snapshots.
Image loading...
To create a snapshot, go to the Snapshots tab and click Take snapshot — this will create a copy of the Sandbox’s current state. Below, you can view all other snapshots previously created for this Sandbox.
Snapshots are saved states of the Sandbox at the moment they were taken. You can use them to:
- Run this snapshot in a new sandbox: Uses the snapshot to create a new sandbox
- Revert to this snapshot: Restore the current Sandbox to the state saved in a snapshot.
Permissions
The Permissions tab allows you to manage user/group access to specific sandboxes. It enables you to define what actions users assigned to a particular sandbox are allowed to perform.
How do sandbox permissions work?
Sandbox permissions override project-defined roles. For example, it is possible to grant access to a user with a Viewer role permission to use a sandbox, or restrict access for a user with a Developer role by setting their permission to None (Deny).
Available access levels
The following access levels are available for sandbox permissions:
Manage – Users with the Manage role have full control over the sandbox. They can:
- Edit all sandbox settings.
- Delete sandboxes.
- Manage user permissions.
View-only – Users can only view the sandbox Activity tab but cannot use or modify it.
None (Deny) – No access to the sandbox.
Project role (default) – Permissions will be inherited based on the user's role in the project.
Managing groups and users
You can add both individual users and entire groups to sandbox permissions. Each user or group can be assigned a different access level, allowing for fine-grained control over who can do what with the sandbox.
Settings
The Settings tab contains all configuration options for the Sandbox.
Image loading...
YAML
The YAML tab displays the current Sandbox configuration in YAML format.
Image loading...
Preparing Sandbox with YAML
The YAML configuration allows for easy management and versioning of environments. Example:
yaml- sandbox: my-app-sandbox name: My Application Environment os: ubuntu:24.04 install_commands: |- apt-get update apt-get install curl -y curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - apt-get install -y nodejs run_command: node server.js app_dir: /var/www app_type: CMD endpoints: - www: 80
For detailed information about YAML parameters, see the Sandbox YAML documentation.
Sandbox Folders
Sandbox folders work exactly the same as for projects and pipelines, allowing you to store sandbox servers according to a selected pattern. To add or manage a folder, click the three dots at the top when on the Sandboxes view:
Image loading...
Sandboxes Actions
Sandboxes can be managed using dedicated actions:
- Create Sandbox
- Manage Sandbox
You can find more information in the Sandboxes action documentation.
Last modified on Feb 3, 2026