From workspace to your first approved change

The core loop, start to finish.

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

Prerequisites

A workspace with two services (call them api and worker) and you as Owner. See the quickstart.
A shared variable inherited by both services.

Create LOG_LEVEL in Env Master with value info. Inherit it into both services (Inherit Env Master on each Variables tab).
In the top bar branch selector choose New branch, name it log-level-debug.
In Env Master edit the value to debug and save. The master still says info; the edit is staged.
Open Branches → your branch. Check the diff, then Submit for review.
Open Notifications. On the branch review card choose Approve & merge (as Owner or Admin).
Each service now has a pending decision for LOG_LEVEL. If you staged the change from one service's page, that service is already approved.
Open the other service's notification and approve it.
Open each service's Export tab to confirm LOG_LEVEL=debug.
Open History to see the branch and approval events.

Before approval, an unapproved service's export still shows info.
After approval, its export shows debug.
If you reject instead, that service stays on info and the history records the rejection.

Edit fields disabled: no branch selected.
MERGE_CONFLICT on submit: someone changed LOG_LEVEL after you started; Rebase then submit again.
Approve buttons missing: you need service_admin on that service, or Owner/Admin.

Where next