A Limitation to specify that only the owner of the Content item gets a certain access right.
Identifier | Owner |
Value Class | eZ\Publish\API\Repository\Values\User\Limitation\OwnerLimitation |
Type Class | eZ\Publish\Core\Limitation\OwnerLimitationType |
Criterion used | eZ\Publish\API\Repository\Values\Content\Query\Criterion\UserMetadata( UserMetadata::OWNER ) |
Role Limitation | no |
Possible values
Value | UI value | Description |
1 | "self" | Only the User who is the owner gets access |
2 | "session" | Same as "self" |
Legacy compatibility notes:
- "session" is deprecated and works exactly like "self" in Public API since it has no knowledge of user Sessions
- A User is no longer automatically assumed to be the owner of themselves and gets access to edit themselves when the Owner limitation is used in Public API
Workaround for the OwnerLimitation on Users
To make sure the User gets access to themselves when using OwnerLimitation across 4.x and 5.x, the solution is to change the User to be the owner of their own Content item.
This is accomplished using a privileged user to do the following API calls: