Workspaces changedapi/organization/workspaces
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+174added
Lines−135removed
From line
73
where the diff opens
First seen
30 Sep 2026
this site's first read of the page
Recorded edits10to this page, all time
The whole hunk
from line 73, old and new numbered
/
from line 73
7373
7474 - `compartment_id: string`
7575
76 Identifier for this Workspace's encryption compartment. When you configure a
77 customer-managed encryption key (CMEK) on AWS, reference this value in your
78 KMS key-policy condition so the key is scoped to this compartment. On GCP and
79 Azure, Anthropic enforces the compartment binding automatically; you do not
80 need to reference this value in your key configuration. See the CMEK
81 integration guide for the required key configuration; unless your organization
82 is on Claude Platform on AWS, it includes a separate value used during key
83 validation. On Claude Platform on AWS there is no separate validation value:
84 the key is validated against this Workspace's own value when it is attached, so
85 if your key policy uses the compartment condition, add this value to it before
86 attaching the key.
76 Identifier for this Workspace's encryption compartment. When you configure an
77 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
78 profile, reference this value in your KMS key-policy condition so the key is
79 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
80 binding automatically; you do not need to reference this value in your key
81 configuration. See the CMEK integration guide for the required key
82 configuration; unless your organization is on Claude Platform on AWS, it
83 includes a separate value used during key validation. On Claude Platform on AWS
84 there is no separate validation value: your organization's own key is validated
85 against this Workspace's own value when it is attached, so if its key policy
86 uses the compartment condition, add this value to it before attaching the key.
8787
8888 - `created_at: string`
8989
from line 129
129129 Workspace. Setting this field requires CMEK to be enabled for your
130130 organization. When set, data stored for this Workspace is encrypted with the
131131 referenced key. Create key configurations with the External Keys API. On
132 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
133 single-Region key in the same AWS account and Region as the Workspace. On that
134 platform the key is validated against this Workspace when it is attached, so a
135 key-policy problem is reported as an error on this request. This field is write-once:
136 once a key is attached to a Workspace it cannot be detached or replaced. To
137 rotate key material, rotate the underlying key on your cloud KMS; the
138 `external_key_id` stays the same.
132 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
133 organization's own key must be a single-Region key in the same AWS account and
134 Region as the Workspace. On that platform the key is validated against this
135 Workspace when it is attached, so a key-policy problem is reported as an error
136 on this request. This field is write-once: once a key is attached to a Workspace
137 it cannot be detached or replaced. To rotate key material, rotate the underlying
138 key on your cloud KMS; the `external_key_id` stays the same.
139139
140140 - `name: string`
141141
from line 145
145145
146146 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
147147
148 - `user_profile_id: string or null`
149
150 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.
151
148152- `first_id: string or null`
149153
150154 First ID in the `data` list. Can be used as the `before_id` for the previous page.
from line 191
187191 "env": "prod",
188192 "team": "platform"
189193 },
190 "type": "workspace"
194 "type": "workspace",
195 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
191196 }
192197 ],
193198 "first_id": "first_id",
from line 263
258263 Workspace. Setting this field requires CMEK to be enabled for your
259264 organization. When set, data stored for this Workspace is encrypted with the
260265 referenced key. Create key configurations with the External Keys API. On
261 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
262 single-Region key in the same AWS account and Region as the Workspace. On that
263 platform the key is validated against this Workspace when it is attached, so a
264 key-policy problem is reported as an error on this request. This field is write-once:
265 once a key is attached to a Workspace it cannot be detached or replaced. To
266 rotate key material, rotate the underlying key on your cloud KMS; the
267 `external_key_id` stays the same.
266 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
267 organization's own key must be a single-Region key in the same AWS account and
268 Region as the Workspace. On that platform the key is validated against this
269 Workspace when it is attached, so a key-policy problem is reported as an error
270 on this request. This field is write-once: once a key is attached to a Workspace
271 it cannot be detached or replaced. To rotate key material, rotate the underlying
272 key on your cloud KMS; the `external_key_id` stays the same.
268273
269274- `tags: optional map[string] or null`
270275
271276 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
272277
278- `user_profile_id: optional string or null`
279
280 ID of a user profile to attach to the Workspace. Every inference request through the Workspace must then name this user profile; the API rejects a request that names none or a different one. The user profile can't be replaced or removed later; only deleting the user profile clears it.
281
273282### Returns
274283
275284- `Workspace object`
from line 303
294303
295304 - `compartment_id: string`
296305
297 Identifier for this Workspace's encryption compartment. When you configure a
298 customer-managed encryption key (CMEK) on AWS, reference this value in your
299 KMS key-policy condition so the key is scoped to this compartment. On GCP and
300 Azure, Anthropic enforces the compartment binding automatically; you do not
301 need to reference this value in your key configuration. See the CMEK
302 integration guide for the required key configuration; unless your organization
303 is on Claude Platform on AWS, it includes a separate value used during key
304 validation. On Claude Platform on AWS there is no separate validation value:
305 the key is validated against this Workspace's own value when it is attached, so
306 if your key policy uses the compartment condition, add this value to it before
307 attaching the key.
306 Identifier for this Workspace's encryption compartment. When you configure an
307 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
308 profile, reference this value in your KMS key-policy condition so the key is
309 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
310 binding automatically; you do not need to reference this value in your key
311 configuration. See the CMEK integration guide for the required key
312 configuration; unless your organization is on Claude Platform on AWS, it
313 includes a separate value used during key validation. On Claude Platform on AWS
314 there is no separate validation value: your organization's own key is validated
315 against this Workspace's own value when it is attached, so if its key policy
316 uses the compartment condition, add this value to it before attaching the key.
308317
309318 - `created_at: string`
310319
from line 359
350359 Workspace. Setting this field requires CMEK to be enabled for your
351360 organization. When set, data stored for this Workspace is encrypted with the
352361 referenced key. Create key configurations with the External Keys API. On
353 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
354 single-Region key in the same AWS account and Region as the Workspace. On that
355 platform the key is validated against this Workspace when it is attached, so a
356 key-policy problem is reported as an error on this request. This field is write-once:
357 once a key is attached to a Workspace it cannot be detached or replaced. To
358 rotate key material, rotate the underlying key on your cloud KMS; the
359 `external_key_id` stays the same.
362 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
363 organization's own key must be a single-Region key in the same AWS account and
364 Region as the Workspace. On that platform the key is validated against this
365 Workspace when it is attached, so a key-policy problem is reported as an error
366 on this request. This field is write-once: once a key is attached to a Workspace
367 it cannot be detached or replaced. To rotate key material, rotate the underlying
368 key on your cloud KMS; the `external_key_id` stays the same.
360369
361370 - `name: string`
362371
from line 375
366375
367376 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
368377
378 - `user_profile_id: string or null`
379
380 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.
381
369382### Example
370383
371384```bash
from line 393
380393 "tags": {
381394 "env": "prod",
382395 "team": "platform"
383 }
396 },
397 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
384398 }'
385399```
386400
from line 418
404418 "env": "prod",
405419 "team": "platform"
406420 },
407 "type": "workspace"
421 "type": "workspace",
422 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
408423}
409424```
410425
from line 467
452467
453468 - `compartment_id: string`
454469
455 Identifier for this Workspace's encryption compartment. When you configure a
456 customer-managed encryption key (CMEK) on AWS, reference this value in your
457 KMS key-policy condition so the key is scoped to this compartment. On GCP and
458 Azure, Anthropic enforces the compartment binding automatically; you do not
459 need to reference this value in your key configuration. See the CMEK
460 integration guide for the required key configuration; unless your organization
461 is on Claude Platform on AWS, it includes a separate value used during key
462 validation. On Claude Platform on AWS there is no separate validation value:
463 the key is validated against this Workspace's own value when it is attached, so
464 if your key policy uses the compartment condition, add this value to it before
465 attaching the key.
470 Identifier for this Workspace's encryption compartment. When you configure an
471 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
472 profile, reference this value in your KMS key-policy condition so the key is
473 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
474 binding automatically; you do not need to reference this value in your key
475 configuration. See the CMEK integration guide for the required key
476 configuration; unless your organization is on Claude Platform on AWS, it
477 includes a separate value used during key validation. On Claude Platform on AWS
478 there is no separate validation value: your organization's own key is validated
479 against this Workspace's own value when it is attached, so if its key policy
480 uses the compartment condition, add this value to it before attaching the key.
466481
467482 - `created_at: string`
468483
from line 523
508523 Workspace. Setting this field requires CMEK to be enabled for your
509524 organization. When set, data stored for this Workspace is encrypted with the
510525 referenced key. Create key configurations with the External Keys API. On
511 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
512 single-Region key in the same AWS account and Region as the Workspace. On that
513 platform the key is validated against this Workspace when it is attached, so a
514 key-policy problem is reported as an error on this request. This field is write-once:
515 once a key is attached to a Workspace it cannot be detached or replaced. To
516 rotate key material, rotate the underlying key on your cloud KMS; the
517 `external_key_id` stays the same.
526 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
527 organization's own key must be a single-Region key in the same AWS account and
528 Region as the Workspace. On that platform the key is validated against this
529 Workspace when it is attached, so a key-policy problem is reported as an error
530 on this request. This field is write-once: once a key is attached to a Workspace
531 it cannot be detached or replaced. To rotate key material, rotate the underlying
532 key on your cloud KMS; the `external_key_id` stays the same.
518533
519534 - `name: string`
520535
from line 539
524539
525540 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
526541
542 - `user_profile_id: string or null`
543
544 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.
545
527546### Example
528547
529548```bash
from line 571
552571 "env": "prod",
553572 "team": "platform"
554573 },
555 "type": "workspace"
574 "type": "workspace",
575 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
556576}
557577```
558578
from line 632
612632 Workspace. Setting this field requires CMEK to be enabled for your
613633 organization. When set, data stored for this Workspace is encrypted with the
614634 referenced key. Create key configurations with the External Keys API. On
615 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
616 single-Region key in the same AWS account and Region as the Workspace. On that
617 platform the key is validated against this Workspace when it is attached, so a
618 key-policy problem is reported as an error on this request. This field is write-once:
619 once a key is attached to a Workspace it cannot be detached or replaced. To
620 rotate key material, rotate the underlying key on your cloud KMS; the
621 `external_key_id` stays the same.
635 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
636 organization's own key must be a single-Region key in the same AWS account and
637 Region as the Workspace. On that platform the key is validated against this
638 Workspace when it is attached, so a key-policy problem is reported as an error
639 on this request. This field is write-once: once a key is attached to a Workspace
640 it cannot be detached or replaced. To rotate key material, rotate the underlying
641 key on your cloud KMS; the `external_key_id` stays the same.
622642
623643- `name: optional string`
624644
from line 650
630650
631651 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
632652
653- `user_profile_id: optional string`
654
655 ID of a user profile to attach to the Workspace. Every inference request through the Workspace must then name this user profile; the API rejects a request that names none or a different one. Once set, it can't be replaced or removed (sending the same ID again changes nothing); only deleting the user profile clears it. The default Workspace can't have a user profile.
656
633657### Returns
634658
635659- `Workspace object`
from line 678
654678
655679 - `compartment_id: string`
656680
657 Identifier for this Workspace's encryption compartment. When you configure a
658 customer-managed encryption key (CMEK) on AWS, reference this value in your
659 KMS key-policy condition so the key is scoped to this compartment. On GCP and
660 Azure, Anthropic enforces the compartment binding automatically; you do not
661 need to reference this value in your key configuration. See the CMEK
662 integration guide for the required key configuration; unless your organization
663 is on Claude Platform on AWS, it includes a separate value used during key
664 validation. On Claude Platform on AWS there is no separate validation value:
665 the key is validated against this Workspace's own value when it is attached, so
666 if your key policy uses the compartment condition, add this value to it before
667 attaching the key.
681 Identifier for this Workspace's encryption compartment. When you configure an
682 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
683 profile, reference this value in your KMS key-policy condition so the key is
684 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
685 binding automatically; you do not need to reference this value in your key
686 configuration. See the CMEK integration guide for the required key
687 configuration; unless your organization is on Claude Platform on AWS, it
688 includes a separate value used during key validation. On Claude Platform on AWS
689 there is no separate validation value: your organization's own key is validated
690 against this Workspace's own value when it is attached, so if its key policy
691 uses the compartment condition, add this value to it before attaching the key.
668692
669693 - `created_at: string`
670694
from line 734
710734 Workspace. Setting this field requires CMEK to be enabled for your
711735 organization. When set, data stored for this Workspace is encrypted with the
712736 referenced key. Create key configurations with the External Keys API. On
713 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
714 single-Region key in the same AWS account and Region as the Workspace. On that
715 platform the key is validated against this Workspace when it is attached, so a
716 key-policy problem is reported as an error on this request. This field is write-once:
717 once a key is attached to a Workspace it cannot be detached or replaced. To
718 rotate key material, rotate the underlying key on your cloud KMS; the
719 `external_key_id` stays the same.
737 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
738 organization's own key must be a single-Region key in the same AWS account and
739 Region as the Workspace. On that platform the key is validated against this
740 Workspace when it is attached, so a key-policy problem is reported as an error
741 on this request. This field is write-once: once a key is attached to a Workspace
742 it cannot be detached or replaced. To rotate key material, rotate the underlying
743 key on your cloud KMS; the `external_key_id` stays the same.
720744
721745 - `name: string`
722746
from line 750
726750
727751 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
728752
753 - `user_profile_id: string or null`
754
755 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.
756
729757### Example
730758
731759```bash
from line 767
739767 "tags": {
740768 "env": "prod",
741769 "team": "platform"
742 }
770 },
771 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
743772 }'
744773```
745774
from line 792
763792 "env": "prod",
764793 "team": "platform"
765794 },
766 "type": "workspace"
795 "type": "workspace",
796 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
767797}
768798```
769799
from line 839
809839
810840 - `compartment_id: string`
811841
812 Identifier for this Workspace's encryption compartment. When you configure a
813 customer-managed encryption key (CMEK) on AWS, reference this value in your
814 KMS key-policy condition so the key is scoped to this compartment. On GCP and
815 Azure, Anthropic enforces the compartment binding automatically; you do not
816 need to reference this value in your key configuration. See the CMEK
817 integration guide for the required key configuration; unless your organization
818 is on Claude Platform on AWS, it includes a separate value used during key
819 validation. On Claude Platform on AWS there is no separate validation value:
820 the key is validated against this Workspace's own value when it is attached, so
821 if your key policy uses the compartment condition, add this value to it before
822 attaching the key.
842 Identifier for this Workspace's encryption compartment. When you configure an
843 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
844 profile, reference this value in your KMS key-policy condition so the key is
845 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
846 binding automatically; you do not need to reference this value in your key
847 configuration. See the CMEK integration guide for the required key
848 configuration; unless your organization is on Claude Platform on AWS, it
849 includes a separate value used during key validation. On Claude Platform on AWS
850 there is no separate validation value: your organization's own key is validated
851 against this Workspace's own value when it is attached, so if its key policy
852 uses the compartment condition, add this value to it before attaching the key.
823853
824854 - `created_at: string`
825855
from line 895
865895 Workspace. Setting this field requires CMEK to be enabled for your
866896 organization. When set, data stored for this Workspace is encrypted with the
867897 referenced key. Create key configurations with the External Keys API. On
868 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
869 single-Region key in the same AWS account and Region as the Workspace. On that
870 platform the key is validated against this Workspace when it is attached, so a
871 key-policy problem is reported as an error on this request. This field is write-once:
872 once a key is attached to a Workspace it cannot be detached or replaced. To
873 rotate key material, rotate the underlying key on your cloud KMS; the
874 `external_key_id` stays the same.
898 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
899 organization's own key must be a single-Region key in the same AWS account and
900 Region as the Workspace. On that platform the key is validated against this
901 Workspace when it is attached, so a key-policy problem is reported as an error
902 on this request. This field is write-once: once a key is attached to a Workspace
903 it cannot be detached or replaced. To rotate key material, rotate the underlying
904 key on your cloud KMS; the `external_key_id` stays the same.
875905
876906 - `name: string`
877907
from line 911
881911
882912 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
883913
914 - `user_profile_id: string or null`
915
916 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.
917
884918### Example
885919
886920```bash
from line 944
910944 "env": "prod",
911945 "team": "platform"
912946 },
913 "type": "workspace"
947 "type": "workspace",
948 "user_profile_id": "uprof_01SDCCSbTxrXDpWc1phhtcfK"
914949}
915950```
916951
from line 1075
10401075
10411076 - `compartment_id: string`
10421077
1043 Identifier for this Workspace's encryption compartment. When you configure a
1044 customer-managed encryption key (CMEK) on AWS, reference this value in your
1045 KMS key-policy condition so the key is scoped to this compartment. On GCP and
1046 Azure, Anthropic enforces the compartment binding automatically; you do not
1047 need to reference this value in your key configuration. See the CMEK
1048 integration guide for the required key configuration; unless your organization
1049 is on Claude Platform on AWS, it includes a separate value used during key
1050 validation. On Claude Platform on AWS there is no separate validation value:
1051 the key is validated against this Workspace's own value when it is attached, so
1052 if your key policy uses the compartment condition, add this value to it before
1053 attaching the key.
1078 Identifier for this Workspace's encryption compartment. When you configure an
1079 AWS KMS customer-managed encryption key (CMEK) that isn't bound to a user
1080 profile, reference this value in your KMS key-policy condition so the key is
1081 scoped to this compartment. On GCP and Azure, Anthropic enforces the compartment
1082 binding automatically; you do not need to reference this value in your key
1083 configuration. See the CMEK integration guide for the required key
1084 configuration; unless your organization is on Claude Platform on AWS, it
1085 includes a separate value used during key validation. On Claude Platform on AWS
1086 there is no separate validation value: your organization's own key is validated
1087 against this Workspace's own value when it is attached, so if its key policy
1088 uses the compartment condition, add this value to it before attaching the key.
10541089
10551090 - `created_at: string`
10561091
from line 1131
10961131 Workspace. Setting this field requires CMEK to be enabled for your
10971132 organization. When set, data stored for this Workspace is encrypted with the
10981133 referenced key. Create key configurations with the External Keys API. On
1099 Claude Platform on AWS the value is the AWS KMS key ARN, and the key must be a
1100 single-Region key in the same AWS account and Region as the Workspace. On that
1101 platform the key is validated against this Workspace when it is attached, so a
1102 key-policy problem is reported as an error on this request. This field is write-once:
1103 once a key is attached to a Workspace it cannot be detached or replaced. To
1104 rotate key material, rotate the underlying key on your cloud KMS; the
1105 `external_key_id` stays the same.
1134 Claude Platform on AWS the value for an AWS KMS key is the key's ARN, and your
1135 organization's own key must be a single-Region key in the same AWS account and
1136 Region as the Workspace. On that platform the key is validated against this
1137 Workspace when it is attached, so a key-policy problem is reported as an error
1138 on this request. This field is write-once: once a key is attached to a Workspace
1139 it cannot be detached or replaced. To rotate key material, rotate the underlying
1140 key on your cloud KMS; the `external_key_id` stays the same.
11061141
11071142 - `name: string`
11081143
from line 1147
11121147
11131148 User-defined tags as string key-value pairs. Keys may not begin with `anthropic`.
11141149
1150 - `user_profile_id: string or null`
1151
1152 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.
1153
11151154### Workspace Member
11161155
11171156- `WorkspaceMember object`
from line 1806
17671806 "data": [
17681807 {
17691808 "type": "workspace_member",
1770 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
1809 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
17711810 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
17721811 "workspace_role": "workspace_admin"
17731812 }
from line 1897
18581897 -H 'anthropic-version: 2026-10-21' \
18591898 -H "Authorization: Bearer $ANTHROPIC_API_KEY" \
18601899 -d '{
1861 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
1900 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
18621901 "workspace_role": "workspace_admin"
18631902 }'
18641903```
from line 1907
18681907```json
18691908{
18701909 "type": "workspace_member",
1871 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
1910 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
18721911 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
18731912 "workspace_role": "workspace_admin"
18741913}
from line 1984
19451984```json
19461985{
19471986 "type": "workspace_member",
1948 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
1987 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
19491988 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
19501989 "workspace_role": "workspace_admin"
19511990}
from line 2081
20422081```json
20432082{
20442083 "type": "workspace_member",
2045 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2084 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
20462085 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ",
20472086 "workspace_role": "workspace_admin"
20482087}
from line 2143
21042143```json
21052144{
21062145 "type": "workspace_member_deleted",
2107 "user_id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
2146 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
21082147 "workspace_id": "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ"
21092148}
21102149```
No line in this hunk matches that.