Open a project’s settings
Choose Settings at the foot of the sidebar. The sidebar then holds settings instead of the usual list, with Back to app at the top. Under Projects, choose the repository you want. The Settings page lists the same projects if you would rather start there. A member sees the entries a member can use. Nothing is greyed out for a member: what only an admin can do is not on the page.What everyone in the organisation sees
Snapshot
The snapshot is the prepared sandbox every session in the project starts from. The section shows:- its status: Not built yet, Building, Ready or Failed
- the commit it was built from and when, for example “Built from 9c41e07 on main, 4 Oct 2026 at 14:02.”
- how long the last build took and the size it ended up
- the build log, under View log
- a Rebuild button
Config
The Config section shows thescaling.yml on the project’s default branch as Scaling read it, with the error if it does not parse.
It reads the file from GitHub when you open the page.
If GitHub cannot be reached, or the project has lost access to the repository, the section says that instead, and the snapshot still shows.
The file itself is described in the config file reference.
Processes and services
This section lists what will start, on which port, and the health check that decides it is up: a TCP check on a port, or an HTTP request to a path.What an admin changes
Changes on this page apply to new sessions and to the next wake. A session that is already running keeps what it started with.Egress allowlist
Theegress list in scaling.yml is a request for hosts the stack may reach while the agent runs.
It does not make a host reachable.
An admin approves each host here, and a session can reach only the approved hosts.
The file lives in the repository, and the agent can edit the repository.
If the file alone decided, an agent could add a host in one session and a later session could reach it once that change was merged.
Approval in Settings, outside the repository, closes that.
A host the file requests that nobody has approved is listed as Requested in scaling.yml, not reachable yet.
Choose Approve to allow it.
To approve a host the file does not request, choose Add host, type the name and choose Approve host.
To take a host away, choose Remove.
A host that still has a secret bound to it cannot be removed until you remove that secret.
A host is a plain name such as api.stripe.com.
It has no wildcard, no IP address, no port and no path, and it has at least two parts.
Scaling does not take hosts it already uses for the repository itself or for package registries.
Removing a host from scaling.yml does not remove its approval.
The row stays, marked Not requested in scaling.yml., until you remove it.
Brokered secrets
A brokered secret is a value Scaling sends to one host, in one header, on the sandbox’s behalf. The agent never holds it. Choose Add secret, pick an approved host, give the header name, for exampleauthorization, paste the value and choose Save secret.
You can only bind a secret to a host that is approved, so approve the host first.
The value is hidden as you type it and never shown after saving.
A value is at least 16 characters, so that Scaling can tell it apart from ordinary text and keep it out of every log.
After saving, the row shows the header, the host and the date it was set, and nothing else.
Nobody can read the value back through Scaling, including you.
To change it choose Replace and paste the new value.
To stop sending it choose Remove and confirm.
A header name is letters, digits and hyphens.
A few headers that control the connection itself, such as host and content-length, cannot be set.
A host and header pair can carry one secret: replace it instead of adding a second.
Usage caps
Three limits apply to every session in the project:
Each field shows the range it accepts.
Using the defaults. shows until someone sets different values.
The save button stays off until a value changes.
When the project already has the most sessions in progress that its cap allows, a new session is refused and the message says to wait for one to finish or ask an admin to raise the limit.