ibau Setup
Taskadmin
Prerequisites
- Administrative access: access to ibau Settings in the Baucore app navigation.
- Provider entitlement: a valid ibau subscription and credentials supplied through the implementation process.
Permissions
| Permission set | Effect |
|---|---|
| Baucore ibau Admin | Grants access to ibau Settings, Research, and Subscription features. |
| Baucore ibau | Grants access to ibau Research and Subscription features. |
Step-by-step walkthrough
1. Open the Settings page
Open the ibau Settings workspace, where all provider behavior is configured — navigate to the ibau Settings page from the app navigation.
2. Setup sub-section
Configure provider readiness, license usage, and who is allowed to operate it.
| Configuration area | Why it matters |
|---|---|
| Connection status | Prevents sync attempts when the provider isn’t active |
| License usage | Keeps assignments within entitlement |
| User assignment model | Controls who can operate and administer provider-driven actions |
3. Options sub-section
Set global integration defaults for creation, sync visibility, and background processing.
| Option | Effect |
|---|---|
| Endpoint URL | Determines where requests are sent |
| New Project as | Routes created records to the chosen object |
| New company as lead | Company becomes Lead or Account based on state |
| New contact as lead | Contact becomes Lead or Contact based on state |
| Show Manual Sync | Users can trigger the guided sync flow |
| Show Auto Sync | Records can sync in background mode |
| Show Unlink | Users can detach a Salesforce record from its provider source |
| Project Sync Flow | Uses a named flow for the manual sync path |
| Reset access token | Deletes the currently used access token |
| Scheduler Active | Automated update polling/sync is active |
| Terminate Background Sync | Background sync processing is halted |
Recommended configuration order:
- Confirm Endpoint URL.
- Set record creation defaults (project, company, contact).
- Define the user sync surface (manual, auto, unlink).
- Set a custom Project Sync Flow if required.
- Activate the scheduler only once background operations are approved.
4. Mapping sub-section
Define how provider payload fields map into Salesforce target fields.
| Field/control | Meaning |
|---|---|
| Target field | Salesforce destination field |
| Provider field | Source field from the ibau payload |
| Default value | Fallback value when the source is missing or not used |
| Overwrite | Allows the inbound value to overwrite an existing value |
| Hide field | Suppresses the field from selected experience contexts |
| Notify on Chatter | Triggers Chatter notification behavior for mapped updates |
See ibau for the country/address ISO mapping requirement and the mandatory post-upgrade Person picklist value on Prov Field Mapping → Type — both are easy to miss during initial setup.
Validation checklist after setup
| Checkpoint | Pass criteria |
|---|---|
| Provider status | Active |
| Licensing | Assigned users within available capacity |
| Connection values | Endpoint URL validated |
| Creation behavior | Project/company/contact defaults aligned with policy |
| Sync behavior | Manual/auto/unlink/scheduler settings approved |
| Mapping quality | Required rows reviewed and saved |
| End-to-end sanity | Behavior confirmed in the Research and Subscriptions flows |