is_system is true), onlyis_default can change.permissions changes, holders lose any legacy access to each kind ofpermissions changed but the new access could not be recorded, the call still returns 200 with the new definition and no consistency token, while what holders can do may still follow the old definition. Saving the same definition again doesn't repair that; only a later change to permissions records it again.curl --location --globoff --request PUT 'https:///api/v2/permission-sets/' \
--header 'Organization-Id;' \
--header 'Ocp-Apim-Subscription-Key: ' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--data '{
"permissions": {
"agents": {
"view": "all",
"edit": "team",
"delete": null,
"publish": "own",
"create": true
}
}
}'{
"success": true,
"message": "Permission set updated successfully",
"data": {
"permission_set": {
"id": "6f1c2d3e-4b5a-4c7d-8e9f-0a1b2c3d4e5f",
"organization_id": 12,
"name": "Agent Editors",
"description": "Can view every assistant and edit the ones their teams administer",
"is_default": false,
"is_system": false,
"is_deleted": false,
"permissions": {
"agents": {
"view": "all",
"edit": "team",
"delete": null,
"publish": null,
"create": false
}
}
}
}
}