Permissions

Get the current user's permissions on a Content Fragment

This operation returns the list of permissions the user has over a specific Content Fragment.

SecuritybearerAuth
Request
path Parameters
fragmentId
required
string <uuid> (UUID)

Content Fragment unique identifier

Example: 49af775d-0e7a-46c3-913d-00f762528373
Responses
200

OK

400

Bad Request. Indicates that the server cannot or will not process the request due to something that is perceived to be a client error. The Problem Details object will provide more information about the exact cause.

404

Not Found. Indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

406

Not Acceptable. 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.

500

Internal Server Error. Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

get/cf/fragments/{fragmentId}/permissions
Request samples 
Response samples 
application/json
{
  • "items": [
    ]
}
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 the /content/dam, the /conf or the /content/launches directory. For folders within /content/launches, the permissions returned describe whether the user can read and create launches in that folder.


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 the /content/dam, the /conf or the /content/launches directory. For folders within /content/launches, the permissions returned describe whether the user can read and create launches in that folder.


 
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" "CREATE_LAUNCH" "CHECKIN" "CHECKOUT"  
Responses 
200
OK


400
Bad Request.
Indicates that the server cannot or will not process the request due to something that is perceived to be a client error. The Problem Details object will provide more information about the exact cause.


406
Not Acceptable.
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
Content Too Large. Indicates that the server is refusing to process a request because the request content is larger than the server is willing or able to process.


415
Unsupported Media Type. Indicates that the origin server is refusing to service the request because the content is in a format not supported by this method on the target resource.


500
Internal Server Error. Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.


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