-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Description
π Description:
Hello,
We are using the ConnectAccountOnboarding
component in our application and would love to have more control over the user experience, especially in the following areas:
β Requested Features
1. Field-level control
We'd like to be able to configure certain behaviors on individual fields:
- β Force specific fields to appear, even if not part of
eventually_due
- ποΈ Hide fields if already prefilled
- π Make fields read-only if already prefilled (prevent users from editing them)
2. Disable "Skip" button
We are requesting the ability to disable the "Skip" button either:
- Globally (for the entire onboarding flow)
- Or selectively (for specific steps such as
representative
,company
, etc.)
Currently, users can sometimes click "Skip" on steps that are essential β like identity documents or banking details. This can lead to:
- Users believing the onboarding is complete, when itβs not
- Confusion about what's missing
- KYC failure without clear feedback
π‘ Example proposed configuration
<ConnectAccountOnboarding
collectionOptions={{
fields: 'eventually_due',
futureRequirements: 'include',
customization: {
forceFields: ['representative.document'], // force fields to show
readonlyIfPrefilled: ['email'],
hideIfPrefilled: ['support_phone'],
disableIgnoreForAllSteps: true, // π disable all "Skip" buttons
disableIgnoreForSteps: ['representative', 'company'], // π or just some steps
},
}}
/>
π This would help improve the reliability and clarity of the onboarding process for end users, and prevent accidental skips of critical compliance steps.
Thanks for considering this enhancement π
radovicstef
Metadata
Metadata
Assignees
Labels
No labels