Salesforce
Mental Model
Forge is a web layer that sits in front of your Salesforce org. It accelerates event-planning workflows without replacing Salesforce as the place where records actually live.

Salesforce is the system of record
Every record Forge creates or updates (events, attendees, sessions, tickets, speakers, sponsors, forms) is written to Salesforce through the standard REST and Composite APIs. If you stopped using Forge tomorrow, everything would still be in your org exactly as you left it.
Forge does keep some data of its own so that screens load quickly. Knowing what it keeps tells you what to expect when you edit data directly in Salesforce.
| Where | What it holds | How long |
|---|---|---|
| Salesforce | All customer records: events, attendees, contacts, forms, answers, transactions, speakers, sponsors. | Indefinitely. Your org controls retention. |
| Forge database | Operational state: your org's connection, encrypted OAuth tokens, sessions, audience lists as Salesforce IDs only, email job definitions and audit logs. It also holds a read cache of record fields (see Sync, Cache and Audit for the object list). | The read cache is refreshed from Salesforce on a schedule. Audit logs are kept; Forge does not purge them automatically. |
| Short-lived cache (Redis) | Attendee display names and emails, plus metadata, layouts and configuration. | Attendee data up to 2 hours by default; other entries minutes. |
- The read cache keeps IDs, statuses, dates, counts and non-personal names such as event, ticket and session names. Attendee and session-attendee names, emails and phone numbers are deliberately left out of it.
- There is one narrow exception: for staff and speaker name lookups, Forge mirrors a Contact's name, email and title. The mirror is skipped automatically for orgs with more than 50,000 Contacts.
- Form answers are saved to Salesforce. While a checkout is in progress they are held only in a short-lived encrypted cache.
Just-in-time (JIT) derivation
When a Forge screen needs personal data, such as an attendee's name or email address, it fetches it from Salesforce at request time. The value may be held briefly in an encrypted Redis cache to reduce API calls, but it is not written to the database's record cache and is not logged.
Consequence of JIT
Data edited directly in Salesforce can look stale in Forge for up to two hours while the short-lived cache holds the previous value. Use the refresh control on a list or detail screen to fetch fresh data. For everything at once, an org admin can use Refresh All Caches on Admin > Salesforce Caching.
Forge honors Salesforce permissions
When you sign in, Forge asks Salesforce for a token that belongs to you, and every Salesforce call you make from the app runs as you. Record ownership, Last Modified By, sharing, object permissions and field-level security are therefore yours, not the integration user's. Forge checks object-level Create, Read, Edit and Delete as well as field-level security: screens and actions you have no object access to are hidden or refused, and fields you cannot read are hidden. Fields you can read but not edit are greyed out. Validation rules, triggers and Flows run on every Forge write exactly as they do for a save inside Salesforce, and a failure shows Salesforce's own message. Forge has no permission layer that can override your org's configuration. Permission changes take effect in Forge within about a minute.
The org's connected Salesforce user (the Username shown on Admin > Org) is used only for work with no signed-in staff member: portals, public pages, volunteer check-in, scheduled cache sync and other background jobs. If your own Salesforce token is missing or revoked, Forge asks you to reconnect; it never falls back to the integration user's access.
Deep links to Salesforce records
Every Salesforce-backed surface in Forge displays a Salesforce record icon that opens the underlying record in your org in a new tab. You can jump from a Forge attendee row straight to the conference360__Attendee__c record in Salesforce without leaving your workflow.
What this means for admins
| If you want to... | Do this | Why |
|---|---|---|
| See a change you made in Salesforce right away | Use the refresh control on the Forge screen. For a broad refresh, go to Admin > Salesforce Caching and choose Refresh All Caches. | Forge reads from a cache for speed. Edits made directly in Salesforce show up on the next sync or refresh. |
| Keep the Forge connection from breaking when someone leaves | Connect Forge with a dedicated integration user rather than a personal account (see For Salesforce Admins). | Background sync and the connection itself run as the connected user. |
| Control who sees which fields | Set field-level security on permission sets in Salesforce, then wait about a minute. | Forge reads each person's field access from Salesforce; it does not keep its own copy of your security model. |
| Understand where a value came from | Open the record with the Salesforce icon and check the field history there. | Salesforce is the only place the record of truth lives. |
One-sentence summary
Forge reads and writes to Salesforce. Salesforce stores the data. Forge shows the UI and keeps a fast read cache of non-personal fields.