Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.319 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

Archive Workspace changedapi/beta/organization/workspaces/archive

Nearest release: v2.1.315, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+24added
Lines−19removed
From line 45 where the diff opens
First seen 26 Aug 2026 this site's first read of the page
Recorded edits9to this page, all time

The whole hunk

from line 45, old and new numbered
/
lines
from line 45
4545 
4646 - `compartment_id: string`
4747 
48 Identifier for this Workspace's encryption compartment. When you configure a
49 customer-managed encryption key (CMEK) on AWS, reference this value in your
50 KMS key-policy condition so the key is scoped to this compartment. On GCP and
51 Azure, Anthropic enforces the compartment binding automatically; you do not
52 need to reference this value in your key configuration. See the CMEK
53 integration guide for the required key configuration; unless your organization
54 is on Claude Platform on AWS, it includes a separate value used during key
55 validation. On Claude Platform on AWS there is no separate validation value:
56 the key is validated against this Workspace's own value when it is attached, so
57 if your key policy uses the compartment condition, add this value to it before
58 attaching the key.
48 Identifier for this Workspace's encryption compartment. When you configure an
49 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
50 profile, reference this value in your KMS key-policy condition so the key is
51 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
52 binding automatically; you do not need to reference this value in your key
53 configuration. See the CMEK integration guide for the required key
54 configuration; unless your organization is on Claude Platform on AWS, it
55 includes a separate value used during key validation. On Claude Platform on AWS
56 there is no separate validation value: your organization's own key is validated
57 against this Workspace's own value when it is attached, so if its key policy
58 uses the compartment condition, add this value to it before attaching the key.
5959 
6060 - `created_at: string`
6161 
from line 101
101101 Workspace. Setting this field requires CMEK to be enabled for your
102102 organization. When set, data stored for this Workspace is encrypted with the
103103 referenced key. Create key configurations with the External Keys API. On
104 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
105 single-Region key in the same AWS account and Region as the Workspace. On that
106 platform the key is validated against this Workspace when it is attached, so a
107 key-policy problem is reported as an error on this request. This field is write-once:
108 once a key is attached to a Workspace it cannot be detached or replaced. To
109 rotate key material, rotate the underlying key on your cloud KMS; the
110 `external_key_id` stays the same.
104 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
105 organization's own key must be a single-Region key in the same AWS account and
106 Region as the Workspace. On that platform the key is validated against this
107 Workspace when it is attached, so a key-policy problem is reported as an error
108 on this request. This field is write-once: once a key is attached to a Workspace
109 it cannot be detached or replaced. To rotate key material, rotate the underlying
110 key on your cloud KMS; the `external_key_id` stays the same.
111111 
112112 - `name: string`
113113 
from line 117
117117 
118118 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
119119 
120 - `user_profile_id: string or null`
121 
122 ID of the user profile attached to the Workspace, or null if it has none. Every inference request through a Workspace that has a user profile must name that profile.
123 
120124## Example
121125 
122126```bash
from line 150
146150 "env": "prod",
147151 "team": "platform"
148152 },
149 "type": "workspace"
153 "type": "workspace",
154 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
150155}
151156```
152157 
Feedback