PranavNagrecha/AwesomeSalesforceSkills / skills/admin/client-onboarding-design
client-onboarding-design
VerifiedUse this skill when designing the FSC client onboarding process — mapping document collection touchpoints, approval steps, compliance checkpoint sequencing, and welcome journey handoffs. Trigger keywords: client onboarding design, onboarding workflow requirements, document collection flow, compliance checkpoint, welcome journey, intake process design. NOT for configuring the Action Plan template itself — use admin/fsc-action-plans. NOT for OmniScript screen and branching requirements — use admin/omniscript-flow-design-requirements.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| references/examples.md | markdown | 8.1 KB |
| references/gotchas.md | markdown | 8.0 KB |
| references/llm-anti-patterns.md | markdown | 7.8 KB |
| references/metadata-examples.md | markdown | 13.8 KB |
| references/well-architected.md | markdown | 6.5 KB |
| scripts/check_client_onboarding_design.pyexecutable | script | 6.3 KB |
| templates/client-onboarding-design-template.md | markdown | 4.9 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — Client Onboarding Design
## Relevant Pillars
- **Operational Excellence** — The most directly relevant pillar. A well-designed onboarding process establishes clear ownership, defined SLAs, governance for process changes (clone-and-republish versioning), and monitoring for in-progress onboarding journeys. Poorly governed onboarding processes degrade operationally over time: templates proliferate without naming conventions, ownership is unclear, and compliance changes are made by emergency workaround.
- **Security** — Compliance checkpoint sequencing is a security and regulatory concern. KYC/AML identity verification, beneficial ownership disclosure, and consent capture must occur in the correct order and must be enforced by the platform (required tasks, approval gates) rather than by convention alone. A process design that relies on advisors manually following a sequence without platform enforcement is a security and audit risk.
- **Reliability** — The onboarding process must behave consistently across all clients. Platform-enforced gates (required Action Plan tasks, approval steps) provide reliability that manual checklists and email reminders do not. The in-flight plan policy during version transitions is a reliability concern: clients should never experience an inconsistent onboarding sequence due to an unmanaged template update.
- **Adaptability** — The template versioning governance design directly addresses adaptability. A process that cannot be safely updated post-launch is fragile. The clone-and-republish pattern, combined with a named owner and change protocol, makes the onboarding process adaptable to regulatory changes without requiring a full re-implementation.
- **Performance** — Less directly relevant at the process design layer, but the decision to split large task sequences across multiple Action Plan phases (UNVERIFIED (2026-10-03): the often-quoted 75-item limit is not in the guides read; test large templates) and the choice between OmniStudio and Screen Flow have downstream performance implications that should be flagged in the design brief.
## Architectural Tradeoffs
**OmniStudio vs. Screen Flow for intake:** OmniStudio OmniScripts offer a richer, more flexible intake experience with declarative branching and reusable DataRaptor integration steps. Screen Flows provide the same core capability with no additional license cost and are sufficient for most onboarding intake scenarios. The tradeoff is feature richness vs. license cost and implementation complexity. For orgs already licensing OmniStudio, OmniScript is the preferred choice. For orgs without OmniStudio, Screen Flow is the correct tool and should not be treated as a compromise — it is the standard platform capability.
**Platform-enforced gates vs. convention-based process:** Required items with dependencies (`OnPreviousItemCompleted`) in Action Plans, and approval steps in Approval Processes, enforce compliance checkpoints at the platform level. A required flag alone does not create order. Convention-based processes (e.g., "advisors know not to send funding instructions before KYC is cleared") are unreliable and not auditable. Well-Architected FSC onboarding uses platform enforcement for all mandatory compliance checkpoints.
**Single monolithic template vs. phased templates:** A single large template is simpler to manage but may hit an item ceiling (UNVERIFIED (2026-10-03): no limit is documented in the guides read) and creates a single point of failure for version updates (any change requires retiring the entire template). Phased templates (one per onboarding stage) are more modular, stay well under the task limit, and allow compliance to update a single phase without touching the rest of the onboarding sequence. For complex onboarding processes, phased templates are the more adaptable and reliable design.
## Anti-Patterns
1. **Designing for OmniStudio without confirming license** — Producing an OmniScript-based intake design before confirming OmniStudio license availability creates rework risk and can block implementation entirely. The correct approach is to confirm licensing in the design phase and select the intake tool accordingly.
2. **Omitting template versioning governance from the initial design** — Treating the clone-and-republish constraint as an implementation detail rather than a process design requirement results in no governance plan when the first post-launch compliance change arrives. Versioning governance must be part of the process design deliverable, not an afterthought.
3. **Sequential compliance checks enforced by convention, not platform** — Designing an onboarding process where compliance checkpoints are communicated as instructions to advisors (rather than required tasks or approval gates) produces an unauditable process that will fail regulatory review. All mandatory compliance checkpoints must be enforced by the platform.
## Official Sources Used
Read for the 2026-10-03 pass (fetched with plain `curl`; line numbers cite the `pdftotext -layout` extraction):
- Metadata API Developer Guide, Summer '26: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf (ActionPlanTemplate special access, fields, item dependencies, sample, and manifest L15080-15365; DocumentChecklistSettings L55674-55735; DocumentType L55744-55800)
- Object Reference for the Salesforce Platform, Summer '26: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf (ActionPlan version binding, `IsUsingHolidayHours`, and parent objects L21594-21775; ActionPlanItem `ItemEntityType` L21822-21846; ActionPlanTemplate L21909-22010; ActionPlanTemplateItem L22217-22300; ActionPlanTemplateVersion status values L22670-22765)
- Financial Services Cloud Developer Guide, Summer '26: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/fsc_dev_guide.pdf (DocumentChecklistItem fields, `IsRequired` properties, and `Status` values L14520-14740)
Listed by the original author and not re-read in this pass (help.salesforce.com and architect.salesforce.com do not serve article content to plain HTTP clients):
- Action Plans Overview, FSC Admin Guide (help.salesforce.com): cited for template immutability, object support, and launch mechanics
- Financial Services Cloud Administrator Guide (help.salesforce.com): cited for FSC feature and licence context, including OmniStudio as a separately licensed add-on
- Salesforce Well-Architected Overview (architect.salesforce.com): Operational Excellence and Adaptability framing for process governance and versioning design
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |