OneEnv documentation
OneEnv governs configuration that many services share. These pages describe what is actually built, using the names you see in the app. Anything that is partial or missing is marked as such on the limitations page.
New here? Read What is OneEnv?, then Core concepts, then follow the Quickstart. For background that does not depend on OneEnv, see the governance guide and the blog.
Getting started
- What is OneEnv?A definition, what it governs, and what it deliberately does not do.
- Who should use OneEnv?An honest fit check before you set anything up.
- Core conceptsEight ideas that explain every screen in the app.
- QuickstartFrom zero to a service inheriting a shared variable.
- Invite team membersIncluding the one thing that surprises people: invitations do not send an email.
Core features
- Environment variable governanceOne shared definition, many consumers, and a reviewed path for changing it.
- Branching and staged changesA Git-style branch for configuration, minus the merge-conflict markers.
- Change reviews and approvalsTwo gates, deliberately: the branch, then each consumer.
- Notifications and propagationPropagation in OneEnv is a decision, not a push.
- Database structure managementGoverning the shape of a database that several services read.
- API contract managementTrack who consumes a route and gate changes to it.
- Validation rule managementDefine a rule once; see everything that depends on it.
- Audit history and reportingAnswering 'who changed this and who agreed?' from data.
- Permissions and access controlTwo layers: a workspace role, and a permission level per service.
- Export and CI accessOneEnv exports configuration; your pipeline pulls it.
Workflows
- From workspace to your first approved changeThe core loop, start to finish.
- Update a shared environment variableIncluding what to do when a branch is out of date.
- Change an API contractA route change, its consumers, and its risk score.
- Review a database structure changeAdd a column, find who reads that table, collect their decisions.
- Manage a change affecting multiple servicesWhen one branch has many consumers who answer at different speeds.