Update a permission set

Update a permission set's name, description, default flag, or permission scopes.

Note: system permission sets (is_system=True) reject changes to name,
description, and permissions with a 403 — only is_default may be toggled
on them, so admins can change which system preset new members auto-assign to.

Path Parameters:

permission_set_id (uuid): ID of the permission set to update.

Request Body:
All fields are optional. Providing permissions triggers a SpiceDB scope sync.
If any of edit/delete/publish is broader than view, view is
automatically escalated to match (to all if the broader scopes mix team
and project, since neither implies the other).

Request Headers:

X-Organization-Id (int, optional): Override the org scoping these permission sets.
Requires manage (admin) access to the specified organization.

Returns:

The updated permission set under data.permission_set.

X-Authorization-Consistency-Token (string): Authorization consistency token returned after a write operation. Pass this in subsequent read requests to ensure read-after-write consistency.

Current Version:

2.0.0

curl --location --globoff --request PUT 'https:///api/v2/permission-sets/' \ --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": "string", "data": { "permission_set": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "organization_id": 0, "name": "string", "description": "string", "is_default": true, "is_system": true, "is_deleted": true, "permissions": { "property1": "string", "property2": "string" } } } }

Update a permission set

Request

Responses