Apex classes and Visualforce pages in Vlocity are enabled for which Profiles during package installation?

Apex classes and Visualforce pages in Vlocity are enabled for which Profiles during package installation?

• A. All Profiles
• B. No Profiles
• C. Only Custom Profiles
• D. Only Standard Profiles

Answer: (B)

During package installation in Vlocity, Apex classes and Visualforce pages are not enabled for any Profiles by default. This means that after installing a Vlocity package, the administrator must manually grant access to the Apex classes and Visualforce pages for specific profiles or permission sets as needed. This process is a security measure designed to ensure that sensitive code and UI components are only accessible to users who have been explicitly granted permission. By defaulting to no access, the system requires a deliberate action from the administrator, which helps organizations control the access to custom logic and user interfaces more effectively. Profiles, whether they are standard or custom, require configuration to ensure that the right level of access is provided according to the organization's security requirements, thus starting with no permissions ensures that there are no unintended access permissions.

During package installation in Vlocity, Apex classes and Visualforce pages are not enabled for any Profiles by default. This means that after installing a Vlocity package, the administrator must manually grant access to the Apex classes and Visualforce pages for specific profiles or permission sets as needed.

This process is a security measure designed to ensure that sensitive code and UI components are only accessible to users who have been explicitly granted permission. By defaulting to no access, the system requires a deliberate action from the administrator, which helps organizations control the access to custom logic and user interfaces more effectively.

Profiles, whether they are standard or custom, require configuration to ensure that the right level of access is provided according to the organization's security requirements, thus starting with no permissions ensures that there are no unintended access permissions.