Stratus Cloud Solutions Stratus Docs
Documentation / Financial Planner User Guide / License and Help
Page 17 of 23

Permissions and Setup

Permissions and Setup

Financial Planner uses standard Salesforce permission sets and Lightning app assignment. No external identity provider or API keys are required.

Permission sets

Permission set Audience Grants
FinPlan_User Planners, advisors, household users Runtime access to Financial Planner LWCs, subscriber-facing Apex, custom objects, and tabs
FinPlan_Admin Implementers, reference-data operators Tax bracket importers, post-install utilities, diagnostics, maintenance Apex, clear-input permission

FinPlan_User follows least-privilege packaging—test classes and admin maintenance are not exposed on the user permission set.

Installation checklist

  1. Install the managed package from AppExchange or a provided package version URL.
  2. Assign FinPlan_User to users who will build or view plans.
  3. Assign FinPlan_Admin only to operators who import tax reference data or run maintenance.
  4. Add the Financial Planner app to user profiles or permission sets.
  5. Confirm object and field-level security for your compliance model (package defaults are subscriber-safe).
  6. Open the app and create a test Financial Plan per Quick Start.

Custom permissions

Custom permission Effect
Clear_Financial_Plan_Input_Data Shows destructive clear-input UI on Import/Export (FinPlan_Admin only in typical deployments)

Authentication and data residency

  • Users authenticate with standard Salesforce login (session-based).
  • All plan data remains in the subscriber org—no outbound financial data transfer during normal operation.
  • HTTPS and org-configured encryption apply per Salesforce platform policies.

License and packaging notes

Financial Planner is distributed as a managed package (Fin_Planner_Clean, namespace finplanner). Licensing is enforced through Salesforce package licensing for AppExchange subscribers. Trial and sandbox behavior follows your Salesforce contract and the package’s listing terms—contact Stratus Cloud Solutions for entitlement questions.

Beta package upgrades may require uninstall/reinstall in test orgs. Production paths should use released package versions. See your implementer runbook before upgrading production.

Related: Troubleshooting, Platform Administration.