Participant Management
A Participant (Beteiligte__c) links an Account, Contact, or Lead to a Project, Project Lead, or Main Project with a specific Role — Architect, Processor, Dealer, Building Owner, and so on. Participants are the record of who influences a project’s outcome, and they drive most of Baucore’s other automation: Opportunity creation, submission results, recommendations, and the stakeholder map all read from Participant data.
Role flags
Every Role picklist value maps to one or more semantic flags, configured in Baucore Admin → Setup Page → Participant Role Settings:
| Flag | Meaning |
|---|---|
| Processor (Verarbeiter) | The company doing the work / winning the tender |
| Buyer | Direct buyer on the project |
| Dealer | Distributor of materials |
| Competitor | Shown in the Producer section of the Submission Result |
| Builder | Gets a status update regardless of Submission selection |
| Specifier / Architect | Gets a status update regardless of Submission selection |
| My Company | Your own company — excluded from Opportunity auto-creation |
Do not delete, deactivate, or rename the API names of Processor, Our Company, Dealer, or Competitor. Translate the labels instead — these values are read directly by automation.
The Participant Management component
Add participantManagement to a Project, Project Lead, Main Project, Account, Contact, or Lead record page:
- Edit the Lightning Record Page.
- Drag Participant Management onto the page from the component list.
- Set
maxHeight(scroll appears automatically past this height) and theallowCreate/allowEdit/allowDeletetoggles. - Optionally set a Field Set to be used on Participant Edit to control which fields appear in the inline edit form.
On a Project/Project Lead/Main Project page it renders as a flat, inline-editable list. On an Account/Contact/Lead page it renders as a read-only tree grid grouped by project, with Main Project participants collapsed as sub-rows.
Duplicate protection
Baucore blocks creating a second participant with the same Role + Account/Contact/Lead + Project (including Project Lead and Main Project). To bulk-load or clean up data that legitimately needs to bypass this, turn on Baucore Setup → Participant Management → Bypass participant duplicated check — and turn it back off once you’re done. To narrow (rather than bypass) this check, see Filter Possible Duplicates Based on Picklist Fields.
Main Project sync
Participants with a role marked as a “Main Project Relevant Role” (configured via the RelRole key in Participant Role Settings) are eligible to sync between a Project/Project Lead and its Main Project — creating one of these roles on a record already linked to a Main Project automatically adds the same participant to the Main Project (duplicates are avoided by checking Role + Account/Contact/Lead first). Whether this happens automatically going forward is controlled by the Sync Main Project Relevant Roles boolean setting; if a Project is missing a participant that already exists on its Main Project, the component shows a hint banner with a one-click Create Missing Participants action regardless of that setting.
Customizing the displayed columns
For Account, Contact, or Lead record pages (the read-only tree grid view), which columns are shown is controlled by the ibsbaucore__ParticipantManagementAcc fieldset on Participant — edit that fieldset to add, remove, or reorder columns.
Loyalty and Performance
Two account-level indicators are calculated automatically from participant win/loss history:
| Indicator | Formula |
|---|---|
| Loyalty | Won ÷ (Won + Won for Competitor) |
| Performance | (Won + Won for Competitor) ÷ (Lost + Won + Won for Competitor) |
Both display as a Red / Yellow / Green traffic light on the Account and on each participant row. Configure the thresholds in Custom Setting → Account Loyalty Thresholds, and recalculate historical values via Baucore Setup → Stakeholder Management → Recalculate Count Won/Lost — see Account Performance and Loyalty Indicator for the full threshold configuration steps.
Populated automatically, not just by hand
Participants aren’t only created manually — they’re also populated by ibau and Barbour ABI sync, by Baucore Inbox email extraction, and by Processor/Dealer recommendation flows.