FAQ-000572 - Custom Settings and Configuration Security / User Permissions and Access Control

Subscribers should have permissions to set up or store new credentials using a custom UI built with Visualforce, Aura, or LWC. This UI captures their input and passes it to an Apex class within the managed package for secure storage. For operations involving protected custom metadata, subscribers shouldn't have direct access to modify the metadata, as it's intended to be securely managed by the package.

The FAQ content is accurate and well-structured, but contains one minor clarity issue. The phrase 'should not have direct access' uses a formal negative construction that could be simplified to 'shouldn't have direct access' to align with conversational tone guidelines while maintaining the same meaning. This change makes the text more natural and easier to read without altering any technical content or security guidance. Regarding security rules selection: 1. **ApexCRUDViolation** - This rule is directly relevant because the FAQ discusses permission management for custom metadata operations. The answer describes scenarios where subscribers should have permissions for certain operations (storing credentials) but not others (modifying protected metadata), which relates to CRUD (Create, Read, Update, Delete) permission violations that this rule detects. 2. **ApexSharingViolations** - This rule applies because the FAQ addresses access control and permission management for custom metadata operations within managed packages. The answer specifically discusses controlling subscriber access to protected custom metadata and secure management within packages, which involves sharing and access control mechanisms that this rule helps enforce.