curl --request PUT \
--url https://api.studio.prisme.ai/v2/workspaces/{workspaceId}/security \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'{
"authorizations": {
"roles": {},
"rules": [
{
"role": [
"<string>"
],
"inverted": true,
"reason": "<string>",
"conditions": {},
"fields": [
"<string>"
],
"priority": 123
}
]
},
"authentication": {
"clientId": "<string>"
}
}Update Security
Update workspace security
curl --request PUT \
--url https://api.studio.prisme.ai/v2/workspaces/{workspaceId}/security \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'{
"authorizations": {
"roles": {},
"rules": [
{
"role": [
"<string>"
],
"inverted": true,
"reason": "<string>",
"conditions": {},
"fields": [
"<string>"
],
"priority": 123
}
]
},
"authentication": {
"clientId": "<string>"
}
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Workspace id
Body
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
The actions that we want to allow/deny
manage, create, read, update, delete, manage_permissions, manage_security, manage_repositories, read_app_dsul, get_usage, aggregate_search, execute, test apps, pages, files, events, workspaces, automations, secrets, secure_secrets, workspace_keyrings, roles, orgs, orgs:members, orgs:groups, orgs:groups:members, orgs:invites, orgs:subscriptions, orgs:roles, orgs:apikeys, orgs:sso, orgs:service-accounts, users, all The roles to which this rule is restricted
If true, will forbid instead of allow
Matching conditions written using a subset of MongoDB queries. This rule will take effect only if conditions match (or are empty). See https://casl.js.org/v5/en/guide/conditions-in-depth
Field-level permissions. When specified, the rule only applies to these fields of the subject.
Response
Success Response
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
Hide child attributes
The actions that we want to allow/deny
manage, create, read, update, delete, manage_permissions, manage_security, manage_repositories, read_app_dsul, get_usage, aggregate_search, execute, test apps, pages, files, events, workspaces, automations, secrets, secure_secrets, workspace_keyrings, roles, orgs, orgs:members, orgs:groups, orgs:groups:members, orgs:invites, orgs:subscriptions, orgs:roles, orgs:apikeys, orgs:sso, orgs:service-accounts, users, all The roles to which this rule is restricted
If true, will forbid instead of allow
Matching conditions written using a subset of MongoDB queries. This rule will take effect only if conditions match (or are empty). See https://casl.js.org/v5/en/guide/conditions-in-depth
Field-level permissions. When specified, the rule only applies to these fields of the subject.
Was this page helpful?