Admin
Field Configuration
Three admin tools control which fields Forge shows and copies. All three are organization-wide: a change affects every user in your org. Field Visibility decides which fields appear on existing records, Event Creation Fields shapes the new-event wizard, and Clone Field Configuration decides what is copied when an event is cloned.
| If you want to... | Use | Where |
|---|---|---|
| Show an extra Salesforce field on an event, session, speaker or sponsor page, hide one, or change its label | Field Visibility | Admin > Field Visibility (/admin/fields) |
| Simplify the new-event wizard, add your own fields to it, or remove steps your team never uses | Event Creation Fields | Admin > Event Creation Fields (/admin/wizard-fields) |
| Control which values carry over when you clone an event | Clone Field Configuration | Admin > Clone Field Configuration (/admin/clone-config) |
Field Visibility
The Field Visibility hub lists eight entities: Event Details, Sessions, Speakers, Sponsors, Attendees, Tickets, Finance and Transactions. Choose one to open its editor. The editor has three tabs, one per surface, and each tab keeps its own saved configuration.
| Surface tab | What it configures |
|---|---|
| List View | A saved field list for the entity's list surface. |
| Detail Panel | A saved field list for the entity's side-panel surface. |
| Full Detail | The fields on the record's full detail view. This is the tab the event pages read: the extra fields shown on event details, sessions, speakers, sponsors and similar sections come from here, and so does the Tickets tab. |
Use the Full Detail tab for changes you want to see on event pages. The List View and Detail Panel tabs save their own lists, but the event pages read the Full Detail list, so changes there may not alter the screens you expect.
Columns in the editor
| Column | What it does | Recommendation |
|---|---|---|
| Move up / Move down | Arrows at the left of a row reorder the fields. Order is saved with the rest. | Put the fields your team looks at first at the top. |
| Visible | Switch. Off hides the field from that surface. The row stays in the list, dimmed, so you can turn it back on. | Hide fields nobody uses to shorten the page. Hiding always wins, even if the same field is also added elsewhere (for example from Record Layouts). |
| Field | The Salesforce field name, read-only. | Use it to be sure which field you are editing. |
| Label | The name users see. Editable. | Rename a field to your organization's wording (for example Venue Name to Location). It changes only what Forge displays, not Salesforce. |
| Widget | How the field is entered: Text, Picklist, Date, Rich Text, Checkbox, Currency, Number or Text Area. | Leave as set unless the field type needs a different editor, for example Text Area for a long note. |
| Read-only | Switch. Marks the field as not editable in Forge. | Use for values that should be maintained in Salesforce only, such as figures set by an integration. |
| Required | Switch. Marks the field as required. | Use sparingly. Only mark a field required if you want every record to have a value. |
Save, reset and defaults
- A banner above the table tells you where the list came from: "Defaults loaded from your Salesforce page layout" (nothing saved yet), "Custom override active" (you have saved a configuration), or a warning that Salesforce defaults could not be loaded and fallback fields are shown.
- Save stores your configuration for that entity and surface. It is only enabled after you change something. The table shows 20 rows at a time with Show more.
- Reset to defaults deletes your saved override for that tab and returns to the fields from the Salesforce page layout.
To add a field to the event pages, make sure the field exists on the Salesforce object and your Salesforce users can read it, then switch it on under Full Detail for the matching entity. Fields users cannot read in Salesforce (field-level security) stay hidden for them regardless of this setting.
Not every entity changes the same kind of screen. Event Details, Sessions, Speakers and Sponsors drive the extra fields on the matching event pages, and Tickets drives the Tickets tab. Attendees, Finance and Transactions can be configured here, but check the target screen after saving to confirm it reflects your change.
Event Creation Fields
Event Creation Fields (Admin > Event Creation Fields) sets which fields appear when someone creates a new event. Changes apply to your whole organization and save as you click, so there is no Save button.
Record type scope
If your Event object has more than one record type, a row of record type buttons appears at the top. With none selected, your choices are global and apply to every event. Click a record type to set choices just for events of that type; those choices override the global ones for that record type only. Click the selected record type again to go back to global. Steps that create other objects (Tickets, Sessions, Speakers, Sponsors) show their own record type buttons when those objects have record types.
Optional steps
Optional steps lets you reorder, or hide, the optional parts of the wizard. Required steps always stay in place.
| Optional step | Can it be hidden? | What happens when hidden |
|---|---|---|
| Donations | No. Always available in the wizard. | Not applicable. |
| Sessions & speakers | Yes | Hidden from the wizard. It is still available from the event after it is created. |
| Sponsors | Yes | Same as above. |
| Navigator | Yes | Same as above. |
| Recurring event | Yes | Same as above. |
| Communications | Yes | Same as above. |
Use the up and down arrows to change the order and the Show switch to hide a step. Each change saves immediately; if saving fails a message asks you to try again.
If your team never runs sessions or sponsors for most events, hide those steps so the wizard is shorter. Nothing is lost: staff can still add them from the event afterwards.
Fields by step
Fields are grouped by wizard step: Details, Tickets, Sessions, Speakers, Sponsors, Donations, Registration Forms, Event Content and Communications. Each field has a switch. Fields marked "Required — always visible" have no switch because the wizard cannot work without them.
| Step | Always visible | Can be turned off |
|---|---|---|
| Details | Event Name, Start Date, End Date | Start Time, End Time, Campaign |
| Tickets | Ticket Name | Ticket Type, Price, Quantity, Description, Sales Start Date, Sales End Date |
| Sessions | Session Name | Start Time, Duration, Location, Capacity, Tracks, Speakers, Visibility |
| Speakers | Speaker Name | Title, Company, Email, Bio, Contact Lookup, Headshot |
| Sponsors | Company Name | Tier, Status, Website URL, Logo |
| Donations | Fund Name | Default Amount, Description |
| Registration Forms | (none) | Before Checkout Form, After Checkout Form, Post-Event Form, Per-Ticket Forms |
| Event Content | (none) | FAQs, Attachments |
| Communications | (none) | Confirmation Email, Day-Of Email, Waitlist Confirmation Email, Spot Available Email |
Every built-in field starts switched on. Turn off the ones your organization never fills in, so event creators see a shorter form.
Custom fields
Under each step, Custom fields lets you add any other Salesforce field from the step's object (for example a custom field on Event, Ticket, Session, Speaker or Sponsor) so it appears in that step of the wizard. The Details step is split into two sections: Identity, When & Where, and Organizer, Venue & Capacity; choose the one that matches where in the wizard you want the field.
- Under Custom fields, type in the Search Salesforce fields box and click a field to add it. Fields already covered by a built-in field are not offered again.
- Use the switch on the field's row to show or hide it without removing it.
- Click the X (Remove) to take it away completely.
| Badge | Meaning | What to do |
|---|---|---|
| Missing in Salesforce | The field was deleted or renamed in Salesforce. | Remove it, and add the replacement field if there is one. |
| Hidden (no read access) | Salesforce field-level security stops users from reading the field. | Ask your Salesforce admin to grant read access, or remove the field. |
| Read-only (no edit access) | Users can see the field but not edit it. | Grant edit access in Salesforce if event creators need to fill it in. |
Clone Field Configuration
Clone Field Configuration controls which fields are copied when an event is cloned (Admin > Clone Field Configuration). It is global: changes apply to all users in your workspace. The field lists respect Salesforce field-level security, so only fields you have create access to are shown.
The page has one expandable section per type of record that can be cloned: Tickets, Sessions, Speakers, Sponsors, Staff, Forms, Email Templates, FAQs, Custom Tabs, Event Content, Event Assets, Keywords, Codes, Tracks, Tables, Badges, Event Settings, Hotel Room Blocks, Budget Expenses, Exhibit Spaces and Logistics Entries. Each header shows how many fields are included.
| Control | What it does | Recommendation |
|---|---|---|
| Field Source: Curated List | You tick exactly which fields to copy under Included Fields. Select all and Deselect all help on long lists. | Use when you want a precise, in-app list and do not want to touch Salesforce. |
| Field Source: Salesforce Field Set | Copies the fields in a Salesforce field set that you choose. If none are found for the object, you can type the field set's developer name (for example Deep_Clone_Layout) instead. | Use when your Salesforce admin already maintains field sets and you want the clone to follow them automatically. |
| Apply to all (All Curated / All Field Set) | Switches every object to the chosen mode in one click. | Use to standardize quickly, then tweak individual objects. |
| Save / Discard | Save applies the changes for that object. Discard drops unsaved edits. An Unsaved changes badge shows when you have edits pending, and leaving the page asks you to confirm. | Save each object you changed. |
What is copied when nothing is configured
- Event: a built-in default list of fields is copied. It covers the name, record type, start and end dates and times, ticket sales dates, cancellation cutoff and the venue and location fields, among others.
- Other record types (tickets, sessions, speakers and so on): every field that Salesforce lets Forge create is copied, excluding system fields, auto-numbered fields, formula (calculated) fields and compound fields such as address blocks.
- A Curated List with nothing ticked, or a field set that cannot be found or resolves to no fields, falls back to that same copy-everything-creatable behavior.
To clone an event but leave out data that should not repeat (for example a sponsor's status or notes), expand that object, choose Curated List, and tick only the fields that should carry over.
If your session expires the page asks you to reload before saving. Reload, then redo your last change.
These three tools are available to org admins only.