Update the permissions that apply to all users on a Dynatrace settings object with the Settings API, for example to share it read-only environment-wide.
| PUT | SaaS | https://{your-environment-id}.apps.dynatrace.com/platform/settings/v1/objects/{object-id}/permissions/all-users |
You use the object-id path parameter to choose a settings object and the permissions field in the request body to set what every user in the environment can do with it. Anyone with write permission on the object can update these permissions. With the admin-access query parameter set to true and the settings:objects:admin permission, you can act on objects you don't own.
To execute this request, you need a platform token or OAuth access token with settings:objects:write scope. To learn how to obtain and use it, see Tokens and authentication.
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| object-id | string | The ID of the required settings object | path | Required |
| admin-access | boolean | If set to true and user has settings:objects:admin permission, the endpoint will act as if the user is the owner of all objects | query | Optional |
| body | Update | The JSON body of the request. Contains the new permissions. | body | Required |
UpdatePermissionsRequest object| Element | Type | Description | Required |
|---|---|---|---|
| permissions | Permissions | Permissions granted to the accessor on this object. The element can hold these values
| Required |
PermissionsList objectPermissions granted to the accessor on this object. r grants read access to view the object; w grants write access to modify the object. Valid values: ["r"] for read-only, ["r", "w"] for read and write.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"permissions": ["r","w"]}
| Code | Description |
|---|---|
| 200 | Success. |
| 400 | - |
| 404 | - |
| 429 | - |
| 503 | - |
| 4XX | - |
| 5XX | - |