# Version environment configuration and keep access live

> **Status: Partially superseded.** Immutable environment revisions remain current, but ownership and sharing are removed; tenant role and archive state are the live authorization inputs. See [Tenant Access](../tenant-access.md).

Supported environment executable configuration is stored as immutable revisions. Revisions initially contain the codebase and will also contain runtime profiles when that sub-configuration is implemented. Publishing configuration inserts a revision and atomically moves the environment's current-revision pointer; it never rewrites historical revision repositories. Automations explicitly follow the latest revision or pin one revision, and every invocation persists the revision it selected before work begins so failed invocations remain traceable.

Sharing, ownership, archive state, and other authorization inputs remain live properties of the environment rather than revisioned configuration. A pinned revision therefore does not preserve access after an environment is unshared or archived. Revision, sharing, ownership, name, and lifecycle mutations append environment activity in the same transaction as the change; presentation and product-wide audit aggregation may evolve independently from this durable record.

The web editor reflects this boundary when inspecting history: a historical selection substitutes only that revision's repositories while continuing to show the current name, owner, sharing, and lifecycle state. Historical mode is entirely read-only to prevent a mixed historical/live view from being mistaken for editable state. Environment and revision IDs are both represented in the canonical URL and browser navigation state.
