# Using the portal

Everything you can do in the WBX Sandbox portal without writing code: start sandboxes and open a terminal in them, look after jobs, manage your team, API keys, network rules and billing.

## Team and roles

Everyone in a team shares its sandboxes, jobs, credit and limits. Each member has one of three roles:

| Role | What they can do |
| --- | --- |
| Owner | Everything, and the main contact for the team. Only owners can change or remove other owners. |
| Admin | Everything except changing owners: API keys and connected apps, network rules, billing, spending limits, default compute class, team members, cancelling jobs. |
| Member | Dashboard, docs, usage and jobs. Can start sandboxes, open a terminal in them and destroy the team's running sandboxes. |

Invite people on the *Team* page with their e-mail address and a role (Member or Admin). The invitation is valid for 7 days and can be revoked until it is accepted. Owners and admins can change a member's role or remove them from the team.

## Start a sandbox

On the *Sandboxes* page open *Start a sandbox*, choose a template and how many minutes it should run, and optionally a compute class, vCPU and memory the network for this sandbox (full internet, allowed destinations only, or no network) and the IP version (your team's default, IPv4, IPv4 and IPv6, or IPv6 only). The sandbox starts right away, is counted against your plan's limits and billed like one started from code.

The same page lists running sandboxes with their name, template, size, expiry time and IPv6 address (if they have one), the sleeping ones in a separate *Asleep* list, and the history of finished ones. *Sleep* puts a running sandbox to sleep (its files are kept), *Wake up* starts it again – a sandbox moved to long-term storage (“Asleep (archived)”) takes a little longer. Any member can end a sandbox with *Destroy*; sleeping sandboxes are deleted after 7 days without use.

## Terminal

*Terminal* next to a running sandbox opens an interactive shell in your browser – handy for looking around when something goes wrong. Closing the tab ends the shell; the sandbox keeps running until its timeout. From your own computer use `wbx connect SB_ID` from the Python SDK instead (see [Terminal](https://sandbox.wbx.cz/docs/sandboxes/terminal.md)).

## Jobs and batches

The *Jobs* page shows your team's background jobs and batches: status, duration, cost, the log, test results and result files you can download. Jobs and their files are kept for a limited time, so download what you need. Owners and admins can cancel a running job or the rest of a batch. Jobs are started from code or by an AI assistant – see [Background jobs](https://sandbox.wbx.cz/docs/jobs.md).

The detail of a job shows its **execution receipt**: what ran (command, the exact template build, input files), how it ran and the checksums of the result files. Once a job has ended, every team member can click **Download signed receipt** – a JSON file signed by WBX that anyone can check with our public key, for example an auditor or another team. See [Signed receipts](https://sandbox.wbx.cz/docs/jobs/receipts.md#signed-receipts).

## API keys and connected apps

On *API keys* owners and admins create and revoke keys. A key can do everything your team can, so use one key per app – then you can revoke it alone. ChatGPT, claude.ai and other assistants connected by signing in appear there as *connected apps*; disconnect one by revoking its key. The same page shows the signing secret for [webhooks](https://sandbox.wbx.cz/docs/jobs/webhooks.md) and lets you rotate it.

## Network rules

The *Network* page sets where your team's sandboxes may connect: **Internet** (any public address), **Allowed destinations only** (the domains and IP ranges you list) or **No network**. Only owners and admins can change it. A single sandbox or job can be made stricter than the team rules, never looser. Private networks, our servers, cloud metadata and outgoing e-mail are always blocked, whatever you set. The same page sets the default **IP version** for new sandboxes – IPv4, IPv4 and IPv6, or IPv6 only (see [IPv6](https://sandbox.wbx.cz/docs/sandboxes/network.md#ipv6)); when you start a sandbox in the portal you can pick another one.

## Usage

*Usage* shows runtime and spend per day, this month's spend with a projection, and which days cost the most. The dashboard adds which templates you use, when your sandboxes run and how they end.

## Billing and credit

Sandboxes and jobs are paid from prepaid credit. On *Billing* owners and admins can:

- choose or change the plan – upgrades start immediately and include the plan's monthly credit, a smaller plan takes effect at the end of the paid month,
- add credit through the payment gateway, and turn on automatic top-up from a saved card when credit falls below an amount you choose (available after the first card payment),
- redeem a voucher code,
- fill in billing details for invoices and download invoices,
- set spending limits for jobs and batches – see [Budget](https://sandbox.wbx.cz/docs/jobs/budget.md).

When credit runs out, new sandboxes can't be started until you top up; running sandboxes continue. Prices are on the [pricing](https://sandbox.wbx.cz/pricing) page.

## Settings

- **Profile and password** – changing your password signs you out everywhere else.
- **Sign-in with Google or GitHub** – connect an account to sign in without a password, or disconnect it.
- **Team name** and **default compute class** for new sandboxes and jobs that don't choose one (owners and admins).
- **Access log** – sign-ins to your account, including failed attempts.

Source: https://sandbox.wbx.cz/docs/portal
