Forge maps every concept in its UI to a Salesforce object. On first connection, Forge reads your org's installed sObjects and writes a per-tenant object-mapping row. If an expected object is not installed, Forge surfaces a 'missing mapping' notice rather than guessing.
:::(Note) (Namespace conventions)
Events objects use the conference360__ namespace. Payments objects use bt_stripe__. Base (forms, visibility rules) uses bt_base__. Fundraising (donations, auctions) uses bt_fundraising__. Standard Salesforce objects (Contact, Lead, Campaign, CampaignMember, Account) are used directly without a namespace prefix.
:::
Events — conference360__ namespace
| Forge concept | Salesforce object | Notes |
|---|---|---|
| Event | conference360__Event__c | Top-level record. One per event. Holds dates, location type, status, visibility, capacity, and branding settings. |
| Session | conference360__Session__c | Child of Event via conference360__Event__c lookup. Models a breakout, workshop, or time-slot within the parent event. |
| Ticket / Item | conference360__Event_Item__c | Child of Event. Covers paid tickets, free tickets, donation items, and guest/add-on products. Controlled by Type__c picklist. |
| Attendee | conference360__Attendee__c | One record per person-event registration. Linked to Contact or Lead via separate lookups. Holds registration status, check-in state, and purchased items. |
| Speaker | conference360__Speaker__c | Child of Event. Profile record for a speaker, including bio, title, company, and status. |
| Sponsor | conference360__Sponsor__c | Child of Event. Holds sponsor tier, account, contact, and status. |
| Form | conference360__Form__c | Registration or survey form definition. Child Form Elements (bt_base__Form_Element__c) define questions and their Salesforce field mappings. |
| Form Submission | conference360__Form_Submission__c | One record per completed registration form. Answers stored in conference360__Form_Submission_Answer__c children. |
| Event Group | conference360__Event_Group__c | Groups multiple events for shared navigation and cross-event reporting. |
| Session Attendee | conference360__Session_Attendee__c | Junction between an Attendee and a Session; tracks per-session enrollment. |
| Speaker Session | conference360__Speaker_Session__c | Junction linking a Speaker to a Session. |
| Budget Expense | conference360__Budget_Expense__c | Line-item budget/expense tracking under an Event. |
| Audience (Segment) | conference360__Attendee__c (filtered) | Segments are SOQL filters over Attendee records; snapshot members stored as SF IDs only in Forge's Postgres. |
| Campaign link | Campaign (standard) | An Event can be linked to a Salesforce Campaign via the Campaign__c lookup; CampaignMember records are used for attendee sync. |
Payments — bt_stripe__ namespace
| Forge concept | Salesforce object | Notes |
|---|---|---|
| Invoice / Order | bt_stripe__Sales_Document__c | Summarises a registrant's purchase. Status moves from Draft → Completed → Voided. Holds line-item totals, balance due, and gateway reference. |
| Transaction | bt_stripe__Transaction__c | One payment attempt. Tracks Transaction_Status__c (Open, Process, Pending, Completed, On Hold, Canceled, Needs Review, Failed) and a separate Payment_Status__c (Authorized, Captured, Refunded, etc.) for the gateway-side payment state. Never stores raw card data. |
| Discount Code | bt_stripe__Code__c | Configures a percentage or fixed-amount discount. Max uses, validity dates, and account restrictions are all stored here. |
| Fee | bt_stripe__Fee__c | Defines a payment-processing or tax fee that applies to items on an event. Type__c is either 'Payment Processing' or 'Tax'. |
| Payment Gateway | bt_stripe__Payment_Gateway__c | Org-level gateway configuration. Supports Stripe, Authorize.Net, and others. Never stores live secrets in the object. |
Base — bt_base__ namespace
| Forge concept | Salesforce object | Notes |
|---|---|---|
| Visibility Rule | bt_base__Rule__c | Defines conditional show/hide logic for items or form elements. Conditions are stored in child bt_base__Rule_Condition__c records. |
| Form Element | bt_base__Form_Element__c | A single question within a Form. Maps_To_Object__c and Maps_To_Field__c wire the answer directly to a Salesforce field on the attendee or contact. |
| Form Submission Answer | bt_base__Form_Submission_Answer__c | Stores the answer to one Form Element for a given submission. Answers that map to PII fields (name, email) are written to the Contact/Lead, never to this object. |
Forms namespace warning
Never reference bt_base__Form_Submission__c or bt_base__Form__c for Forge registration workflows. Forge uses exclusively the conference360__ form and submission schema (conference360__Form__c, conference360__Form_Submission__c, conference360__Form_Submission_Answer__c).
Fundraising — bt_fundraising__ namespace (Beta)
| Forge concept | Salesforce object | Notes |
|---|---|---|
| Donation | bt_fundraising__Donation__c | A single giving transaction. Holds amount, designation, frequency, donor contact/account, and gateway transaction ID. |
| Recurring Gift | bt_fundraising__Recurring_Gift__c | A recurring donation schedule — cadence, amount, next payment date. Driven by Forge's own recurrence engine, never by Stripe Subscriptions. |
| Pledge | bt_fundraising__Pledge__c | A donor commitment to give over time, tracked against fulfilment. |
| Designation | bt_fundraising__Designation__c | Fund bucket that a donation amount is allocated to. |
| Auction | bt_fundraising__Auction__c | An auction event. Type__c indicates Live, Silent, or Timed. |
| Auction Item | bt_fundraising__Auction_Item__c | A lot within an Auction. Holds title, starting bid, reserve, and fair market value. |
| Bid | bt_fundraising__Bid__c | An individual bid placed on an Auction Item. |
| Auction Registration | bt_fundraising__Auction_Registration__c | Registers a bidder to participate in an Auction. |
| P2P Participant | bt_fundraising__P2P_Participant__c | A peer-to-peer fundraising participant record. |
| P2P Team | bt_fundraising__P2P_Team__c | A peer-to-peer fundraising team. |