Stay organized with collections
Save and categorize content based on your preferences.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["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:` or `domain:`, 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."]]],[]]
