[Web] Move environment editing to Admin settings

Organization-shared environments

On Team and Enterprise plans, an Owner can create cloud environments that are shared with every member of the organization. The same role manages everything else on the Cloud environments admin page, including self-hosted environments; the Admin role can't open the page. The full list of roles that can open it is the one for managing server-managed settings.

Shared environments appear in each member's environment selector under an Organization heading, after the member's own environments under Personal, so a team can standardize on one configuration instead of each member recreating it. Selecting a shared environment's settings icon there opens a read-only summary of its configuration for every member, Owners included.

An Owner makes an environment available to the organization in one of two ways:

• Create a shared environment: use the Cloud environments page in admin settings, which is also where Owners edit and archive shared environments. Each one has a name, a network access level, environment variables in .env format, and a setup script.
• Share a personal environment: open one of your own environments for editing in the environment selector, then share it from the Who can use it row. The environment keeps its ID, so sessions and routines that already use it aren't affected, and every member can then see it and start sessions in it.

Owners choose the organization's default environment separately, at claude.ai/admin-settings/claude-code.

Every member's sessions in a shared environment read its variables, so don't include secrets in them. API credentials, which give sessions a key they can't read, aren't available on Team or Enterprise plans yet.