How to Read This Documentation

This documentation hub is built into Forge itself — you can open it any time via the Help link in the sidebar. Here's how it's organized and how to get the most out of it.

Documentation structure

• Welcome — orientation, a 60-second tour, and how Forge relates to your Salesforce org.
• Getting Started — step-by-step guides for logging in, navigating the shell, and completing first-run setup.
• Core Concepts — the mental models you need to use Forge effectively: events, tickets, attendees, forms, payments, and more.
• Tips & FAQs — best practices, common gotchas, troubleshooting steps, and frequently asked questions.
• Glossary — a comprehensive table of Forge terms, their Salesforce equivalents, and industry-standard names.

Block types you'll encounter

• Blue info callouts — additional context or helpful notes.
• Purple Salesforce callouts — how a Forge concept maps to a Salesforce object or field.
• Orange warning callouts — important caveats, especially around PII and irreversible actions.
• Numbered steps — follow these in order to complete a task.
• Tables — comparisons, field mappings, and reference data.
• Figures — annotated screenshots of real Forge screens.

Beta features

Features marked with a Beta badge are available but still evolving. They may have known limitations, and their behavior or UI may change before general availability. You must opt in to beta features from the /beta settings page. Beta features are clearly labeled throughout this documentation.

Salesforce field references

Throughout this documentation, Salesforce API names appear in monospace (e.g., conference360__Event__c) so you can cross-reference them in Salesforce Setup, Apex, or SOQL. You never need to type these API names in Forge itself.

Demo data in examples

Concrete examples in this documentation use a fictional event called "*Planner Conference 2026" (September 15–17, 2026). Screenshots may reference this event. Replace this event's details with your own as you follow along.