Configure cloud environments changedcloud-environments
Nearest release: v2.1.322, published 16 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 10 Nov 2026 18:51 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 10 Nov 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−1removed
From line
98
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits68to this page, all time
The whole hunk
from line 98, old and new numbered
/
from line 98
9898* **Role**: on every plan, you can add and delete secrets on your own environments whatever your role. On Team and Enterprise, Owners hold an organization admin role in your claude.ai organization and Admins don't, which changes what you see in these cases:
9999 * **Your own environment**: without an organization admin role, **Add secret** opens a [shorter form](#add-a-secret-without-the-role)
100100 * **A shared environment**: Owners [add and delete its secrets](#add-a-credential) from admin settings. Without an organization admin role, ask an Owner to add the secret, because the environment's dialog has no **Network secrets** section
101* **Environment type**: an Anthropic-hosted cloud environment that already exists. A [self-hosted environment](https://code.claude.com/docs/en/self-hosted-environments) doesn't have network secrets
101* **Environment type**: an Anthropic-hosted cloud environment. A [self-hosted environment](https://code.claude.com/docs/en/self-hosted-environments) doesn't have network secrets
102102* **API reachability**: the API accepts connections from the internet, because requests leave from Anthropic's network
103103* **Encryption keys**: if your organization uses customer-managed encryption keys, you can't save network secrets
104104
No line in this hunk matches that.