Permissions

Get the current's user permissions on a list of resources

This operation returns the list of permissions the user has over a list of Folder, Content Fragments or Content Fragment Models. The Content Fragments are expected to be within the /content/dam directory, the Content Fragment Models within the /conf directory, and the Folders could be within either /content/dam or the /conf directory.

SecuritybearerAuth
Request
Request Body schema: application/json

Request parameters to retrieve permissions.

paths
required
Array of strings non-empty

The list of resource paths - Content Fragments, Content Fragment Models and Folder - for which the system has to return the list of permissions for a user. The Content Fragments are expected to be within the /content/dam directory, the Content Fragment Models within the /conf directory, and the Folders could be within either /content/dam or the /conf directory.

preferredPermissions
Array of strings (Permission)

The preferred list of permissions to return.

Items Enum: "READ" "EDIT" "RENAME" "DELETE" "PUBLISH" "CREATE_CONTENT_FRAGMENT" "CREATE_CONTENT_FRAGMENT_MODEL"
Responses
200

OK

400

Bad Request. The Problem Details object will provide more information about the exact cause.

406

Unacceptable. indicates that the target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request.

413

"The HTTP 413 Content Too Large response status code indicates that the request entity is larger than limits defined by server; the server might close the connection or return a Retry-After header field. Prior to RFC 9110 the response phrase for the status was Payload Too Large. That name is still widely used."

415

Unsupported Media Type. When provided as a response to a PATCH request, the response will provide an Accept-Patch response header to notify the client what patch document media types are supported.

500

The server encountered an unexpected error. Retrying the request after a certain time could help.

post/cf/permissions
Request samples
application/json
{
  • "paths": [
    ],
  • "preferredPermissions": [
    ]
}
Response samples
application/json
{
  • "items": [
    ]
}