Brands

Get User's Effective Permissions for a Brand

Changed on

The endpoint retrieves the effective permission (role) assigned to the user for a specific brand, identified by its assetId. It evaluates the user's access based on:

  • Direct permissions assigned to the brand.
  • Predefined principals, such as orgEverybody or group-based access rules.
get/brands/{assetId}/effective-permission

Request

  • Base URL: https://cloudstorage.adobe.io/v1
  • URL: https://cloudstorage.adobe.io/v1/brands/{assetId}/effective-permission
  • Auth: HTTP bearer

Path parameters

assetIdstring required

A globally unique identifier for the asset

Example:urn:aaid:sc:US:4f2fc15c-c062-4951-b37b-1f65ed62a174

The ID of the asset to get.

Headers

x-request-idstring
Example:1234567890

The X-Request-Id header is used to identify a request.
It can be used to correlate logs and other resources and is intended to be a non-persistent identifier.

Response

Success - Effective permission for the user for a brand asset

role'edit' | 'comment' | 'undefined'

It describes the level of access granted for an asset to a subject.
Following roles are supported:

  • edit - The subject has edit access to the asset. It includes all permissions of the comment role as well as the ability to share the asset with other users.
  • comment - The subject has comment access to the asset. It includes the ability to view the asset and add comments to it.
  • undefined - In some cases, a permission that cannot be expressed by edit or comment is returned as undefined. The user has some underlying permission to the asset, but the access is not specific enough to be classified as edit or comment. User operations may be limited.

NOTE:
This list is not exhaustive and will be updated as roles are added. Clients should expect new roles to be added in the future.

Example response

{
  "role": "edit"
}

Changes