Environments

An environment is a named workspace inside your tenant, such as Development, Staging or Production. Every test, and every Test Log entry, belongs to exactly one environment. Environments let you keep separate configurations side by side, for example a test against your staging token endpoint and the same test against production.

• Every tenant always has at least one environment. A Default environment is created when you sign up.
• Each user works in one current environment at a time. Test pages and the Test Log show only that environment's content.
• Any member can create, rename, delete and switch environments.
• The number of environments you can create depends on your plan.

Switching environment

Use the Environment dropdown at the top of the sidebar. The page reloads to show the chosen environment's tests and runs.

Your selection is saved to your account, so it is remembered across sign-ins and devices. It is shared between browser tabs: switching in one tab changes the environment for all your tabs.

Managing environments

Go to Environments in the sidebar.

Fields

Field	Required	Supported values
Name	✅	Up to 100 characters. Must be unique within the tenant.
Description		Free text.

Helena also derives a URL-friendly slug from the name. The API returns it. Two names that produce the same slug count as duplicates, so Staging and staging! cannot both exist. A name must contain at least one letter or digit.

Create

Select New environment, enter a name and an optional description, then select Create environment. If your plan's environment limit has been reached, upgrade the plan or delete an environment you no longer need.

Rename

Select Edit on the environment. Renaming keeps all its tests, history and service-account access. Only the name, slug and description change.

Delete

Select Delete on the environment and confirm.

Deleting an environment deletes everything in it

All tests in the environment, their configuration, secrets and OIDC issuers are permanently deleted. Targets that trusted a deleted test's issuer can no longer fetch its keys.

• You cannot delete the tenant's last environment.
• Anyone who had the deleted environment selected is moved to the oldest remaining environment.

Environments and service accounts

A service account can access either all environments, including ones created later, or a chosen set. On the API, any environment the account cannot access returns 404, exactly as if it did not exist.