AI-generated Key Takeaways
-
Revoke access for multiple users from a Looker Studio asset using the
revokeAllPermissions
endpoint. -
Requests to remove users will always return a successful response (
200 OK
), even if the user is invalid or not associated with the asset. -
The request body requires a list of members to remove, specified as
user:
ordomain:
, but owners and the authorized user cannot be removed. -
Successful requests return an updated Permissions object reflecting the changes made.
-
This API call needs authorization with the
https://www.googleapis.com/auth/datastudio
scope.
Remove members from a Looker Studio asset.
To simply the process of removing user access to assets, well-formed requests
always return a 200 OK
response, even if a member is invalid or does not
belong to the Looker Studio asset.
Request
HTTP request
POST https://datastudio.googleapis.com/v1/assets/{assetName}/permissions:revokeAllPermissions
Path parameters
Parameter name | Type | Description |
---|---|---|
assetName | string | The name (ID) id of the asset. |
Authorization
This request requires the authorized user to have sufficient permissions to manage the assets permissions and authorization with the following scope:
Scope |
---|
https://www.googleapis.com/auth/datastudio |
Request body
In the request body, supply the following properties:
Property name | Type | Description |
---|---|---|
members | Array<Member> | A list of members to remove. Owners cannot be removed. The authorized user cannot be removed. |
Response
If successful, this method returns the updated Permissions object.
Example
The following removes two members from a Looker Studio asset.
POST https://datastudio.googleapis.com/v1/assets/assetName/permissions:revokeAllPermissions
Request body:
{
"members": [
"user:gus@gmail.com",
"domain:example.com"
]
}