can_remove_entity_member permission (or the wildcard * permission) on the entity to perform this action — this is resolved from the caller's own entity-access record, not the record being removed.403).400).entity_id, so an access record belonging to a different entity is never matched and the endpoint responds as if it does not exist (404).curl --location --request DELETE '/entity-access/01JABC1234567890ABCDEFGHIJ?entity_id=01HZ9ABCD1234EFGH5678IJKL90' \
--header 'Authorization: Bearer <token>'{
"message": "Entity access removed successfully",
"status": "success",
"data": {
"id": "01JABC1234567890ABCDEFGHIJ",
"deleted": true
}
}