No! The custom objects (Onboarded_Employee__c, Onboarded_Employer__c, etc.) are entirely optional. You can configure the application to sync data directly to your existing Salesforce objects like Contact, Account, Lead, or any custom objects you already use. See the Object Mapping page for details.
Sync frequency depends on your configuration. You can schedule automatic syncs (daily, hourly, etc.) using the scheduler, or run syncs manually on-demand. Most customers sync daily during off-hours.
Yes! Use the SalesforceToOnboardedSync invocable action in Flows to push Salesforce changes to Onboarded™. Configure field mappings with "Outbound" or "Bidirectional" sync direction.
Failed records are logged in Onboarded_Error_Log__c with details about the error. The sync continues processing other records. Failed records can be retried in the next sync.
Batch jobs run as the user who scheduled them, and operations run in USER_MODE. Ensure the scheduling user has:
- The Onboarded™ Admin permission set assigned
- CRUD access to all target objects
- Field-level access to all mapped fields
- Appropriate sharing rules to access records
The application respects Salesforce's field-level security and encryption settings. If you've enabled Shield Platform Encryption on sensitive fields, that encryption applies to synced data.
Use the Salesforce CLI with the --upgrade-type Mixed flag to preserve existing data. Your configurations will be retained during the upgrade.
sf package install --package "04t..." --target-org YourOrg --upgrade-type MixedThe components expose optional Custom Permission gates for these buttons. If your admin has populated the View Document Custom Permission API Name or Employer Task Custom Permission API Name property, only users with BOTH the Onboarded™ HR Representative permission set AND the named Custom Permission will see the button. Without those properties set, the buttons follow the default visibility (HR Rep or Admin). See the Components page's Custom Permission Button Gating section.
On a completed task, Unlock Task lets HR users re-open specific sections of the form so the employee can correct or revise information. Each selected section produces an unlock request to Onboarded™. Unlock requests are processed asynchronously; the row optimistically reverts to incomplete on first success, and a toast indicates all-succeeded, partial-success, or all-failed.
The Authorized Until enrichment requires a Field Mapping for authorized_until on your Task object, both Salesforce Object and Salesforce Field populated. The task name must contain "I-9" (case-insensitive). If both conditions are met, the click on Employer Task should opportunistically refresh the field from Onboarded™. If the field is still not updating, check the Onboarded™ Error Log for failure details.
For technical support, contact:
- Email: support@onboarded.com
- In-app: Use the Help menu in the Onboarded™ portal
- Documentation: docs.onboarded.com