Quickstart

From zero to a service inheriting a shared variable.

By the OneEnv team · Last updated 2026-10-15

Prerequisites

• An email address you can receive a one-time login code on.
• A modern browser. No installation is required.

Step by step

1. Open the login page and enter your email. OneEnv sends a one-time code; enter it. A first-time email creates your account.
2. On the workspaces page choose Create workspace, name it and confirm. You become its Owner.
3. Open Services in the sidebar and choose New service. Create one per application that consumes shared configuration. Names must be unique in the workspace.
4. Open Env Master and choose New Env Master. Enter a Key (for example DATABASE_HOST), an optional description, tick the secret box if the value is sensitive, and set the value.
5. Open a service, go to the Variables tab and choose Inherit Env Master. Pick your key. The service now depends on it.
6. Open the service's Export tab and pick shell, dotenv or HOCON to see the resolved configuration.

What you should see

The service lists the variable as in sync, and the Export preview contains the key with the current value. Secret values are masked everywhere except in the export itself.

Common problems

• A 409 DUPLICATE_KEY means the key or service name already exists in the workspace (archived items still count).
• Edit forms for existing shared values stay disabled until you select or create a branch. That is expected; see the first-change workflow.
• In a local development install the login code prints in the backend log instead of being emailed.