Permissions

Update user permissions on asset

Saves permissions for a user's individual role on a specific asset (host or folder). This endpoint assigns permissions directly to the user's individual role. If the asset inherits permissions, inheritance will be broken automatically before saving. Optionally cascade permissions to descendants (removes their individual permissions). Only admin users can update permissions.

put/api/v1/permissions/user/{userId}/asset/{assetId}

Path parameters

userIdstring required

User ID or email address

assetIdstring required

Asset identifier (host ID or folder inode)

Request body

permissionsobject required

Permission assignments by scope (INDIVIDUAL, HOST, FOLDER, etc.) with permission levels (READ, WRITE, PUBLISH, EDIT_PERMISSIONS, CAN_ADD_CHILDREN)

cascadeboolean

Whether to cascade permissions to all children assets

Example request

{
  "permissions": {
    "INDIVIDUAL": [
      "READ",
      "WRITE"
    ],
    "HOST": [
      "READ"
    ]
  }
}

Response

User permissions updated successfully

i18nMessagesMapobject
permissionsstring[]

Example response

{
  "entity": {
    "userId": "admin@dotcms.com",
    "roleId": "abc-123-def-456",
    "asset": {
      "id": "abc-123-def-456",
      "type": "HOST",
      "name": "demo.dotcms.com",
      "path": "/demo.dotcms.com/application",
      "hostId": "abc-123-def-456",
      "canEditPermissions": true,
      "permissions": {
        "INDIVIDUAL": [
          "READ",
          "WRITE",
          "PUBLISH"
        ],
        "HOST": [
          "READ"
        ]
      }
    }
  }
}

Changes

No recorded changes to this endpoint across all 1 revision of this API.