Object Level Access Control (OLAC) provides granular authorization over individual objects stored within CyberArk Safes.
In a standard Safe configuration, users receive access according to their Safe membership and assigned authorizations. OLAC extends this authorization model by allowing permissions to be managed at the individual-object level.
This is particularly useful when a Safe contains sensitive privileged accounts requiring different access restrictions.
For example, an Active Directory administrator may need to restrict access to a Domain Administrator credential without applying identical restrictions to every account in the same Safe.
However, OLAC introduces an important configuration limitation: once enabled for a Safe, it cannot subsequently be disabled through the supported configuration mechanism .
Therefore, OLAC is unsuitable as a temporary access-control feature.
Administrators should evaluate the long-term authorization model, application dependencies, Safe ownership, and ongoing administration requirements before enabling it.
Option A contradicts OLAC's purpose, which is to provide object-specific authorization. Option C incorrectly suggests that PSM session management becomes universally unavailable. Option D incorrectly states that new objects cannot be stored in the Safe.
The correct architectural recommendation is to design the required granular permissions before permanently enabling OLAC.
[Reference:CyberArk PAM Self-Hosted — Safes, Object Level Access Control, Object Permissions and Safe Configuration Restrictions.]