FAQ-001023 - Flow Security and System Mode / Flow Design Best Practices

Configure Salesforce flows to avoid "System Without Sharing" mode issues by adopting a "least privilege" approach. Run flows in user context by default and only elevate access when absolutely necessary through secure, modular components.

The original answer was unnecessarily verbose with phrases like 'requires adopting a "least privilege" mindset' and 'where flows run in the user context by default' that could be simplified for better clarity. The updated version maintains all the core technical points but uses more direct, conversational language aligned with the brand guidelines. I selected PreventPassingUserDataIntoElementWithoutSharing because this FAQ directly addresses avoiding "system without sharing" mode issues in flows, which is exactly what this rule detects - it prevents passing user data into flow elements that run without sharing restrictions. PreventPassingUserDataIntoElementWithSharing was included because the FAQ discusses the balance between user context and elevated access, and this rule helps identify when user data flows into elements with sharing (user context). ApexSharingViolations relates to the broader sharing context discussion in the FAQ about properly managing access privileges and avoiding system mode issues.