Admin
Setup Checklist, Admin Settings and Vanity Domains
The Setup page (Admin > Setup) walks a new admin through getting a Forge account ready to run events. It is a checklist of sections you work through in order. Each section shows its state: green means done, amber means action needed, and each links to the page where you make the change. Most teams finish in under 15 minutes.
How the page works
- A summary badge at the top counts completed sections out of the total.
- When Salesforce is connected, a banner shows the Org name and whether it is a Sandbox or Production environment.
- Refresh re-reads the status. Use it after you finish a step in another tab, because the checklist does not update by itself.
- Click a section to expand it. Each section has an Open button that takes you to the right settings page.
Setup sections
The checks below are the exact conditions Forge uses to mark a section green.
| Section | Goes green when | What to do | Recommendation |
|---|---|---|---|
| Salesforce Connection | Forge is connected to your org. | Shows Org and Environment (Sandbox or Production). Manage Salesforce connection opens the Salesforce Org Connection page. | Check the Environment label first. Connecting a Sandbox by mistake is the most common setup error; reconnect to Production before inviting the team. |
| Required Apps | The Blackthorn Events, Base and Payments apps are all installed in the org. | Missing apps are listed with a warning icon. Review installed apps opens the installed-packages list on the org page. This section only appears once Forge has finished scanning the org's installed packages. | Install any missing app from Salesforce before using Forge; features that depend on it will not work correctly. |
| Users & Permissions | More than one user exists (the admin account alone is not enough). | Explains the two roles. Planner: full day-to-day access to events, audiences, reports and any optional section your org turned on, but no Admin section. Admin: everything Planner has plus every configurable setting. Current users shows the count. Team members appear after their first login. | Forge reads each person's Salesforce profile and permission sets at sign-in: Modify All Data, Manage Users or Customize Application makes them an Admin, anyone else is a Planner. To change someone's role, change their Salesforce profile or permission sets. Salesforce field-level security and record access still apply per person. |
| Email Domain | The sending domain status is verified. | Shows the domain status (Not configured, pending or verified). Configure email settings opens Admin > Email, where you add the DNS (CNAME) records. | DNS changes usually take 24 to 48 hours, so start this step first. Forge does not use Salesforce org-wide email addresses; sending from Forge is free. If you use Marketing Cloud for email you can skip this step; otherwise make sure the same message is not also sent from Salesforce, or people get duplicates. |
| From Address | A default From address is saved. | Shows Configured or Not set. Set from address opens Admin > Email. | Use a monitored mailbox on your verified domain. It is required before Forge will send any email. |
| Payment Gateway | At least one payment provider is connected. | Shows Connected or Not connected. Manage payment gateways opens gateway settings. | Skip for a free-event org. Connect one before publishing any paid event or ticket. |
| Beacon AI Agent | Beacon is authorized for your user. | Only appears when Beacon is configured for your org. Shows Connected, Needs Salesforce authorization, or Not linked. | Authorize before first use. See the Beacon notes below. |
Beacon AI Agent notes
Beacon is an AI agent that helps planners manage events in natural language. It needs its own Salesforce authorization (a separate Connected App), apart from the Forge connection. Beacon signs each user in as their own Salesforce user, so every user authorizes Beacon once for themselves, from the Authorize Beacon link in the Beacon panel, signing in to Salesforce with their own account.
- Authorize starts the Salesforce login. If Beacon's service is unreachable the step says Beacon is temporarily unavailable; try again later.
- If Forge's own Salesforce connection needs reconnecting, the Beacon panel sends users to an admin on this page instead.
- A Forge user who is not linked to a Salesforce user sees that Beacon isn't available for their account; Forge links them when they sign out and sign back in with their Salesforce account.
- A user below the planner role is told they don't have access to Beacon.
Order that avoids waiting: connect Salesforce, confirm Required Apps, add the email domain DNS records right away (they take the longest), then invite users and connect a payment gateway while DNS propagates.
Only org admins can open the Setup page.
Admin Settings (Admin > Settings)
Admin Settings holds three org-wide switches that apply to every user and save the moment you flip them: Disable Communications (hide Communications from all event pages), Disable Audiences (hide the global Audiences feature) and Open records locked (Event Details opens read-only until someone clicks Edit). The full description, effects and recommendations for each switch are on the Org Settings and MDM guide page.
These switches affect everyone in the org, not just you. When unsure, leave all three off.
Vanity Domains (Admin > Vanity Domains)
A vanity domain is your own web address (for example give.example.org) that Forge recognizes as belonging to your organization. When a visitor reaches Forge on a registered hostname, Forge uses it to work out which organization the public page belongs to, so donation, auction and portal pages can be served on your brand instead of a Forge address. The Vanity Domains page (/admin/vanity-domains) lists your registered hostnames and lets you add or remove them.
| Control | What it does | Recommendation |
|---|---|---|
| Hostname | The address to register, for example give.example.org. It needs at least one dot, each part up to 63 letters, numbers or interior hyphens, and a final ending of at least two letters. If it is not valid, a red hint reads "Enter a valid hostname (e.g. give.example.org)" and Add Domain stays disabled. Forge ignores a leading www. and any port, and stores the name in lowercase. | Use a dedicated subdomain such as give. or events. rather than your main website address. |
| Add Domain | Registers the hostname for your organization. A hostname already registered to another organization is rejected ("This domain is already registered to another tenant"). Each organization can register up to 25 domains. | Register only domains you control. Adding a name here registers it with Forge; it does not create DNS records at your domain provider, so the address itself must also be pointed at Forge by whoever manages your DNS. Contact Blackthorn support if unsure. |
| Remove | Deletes the registration after a confirmation that says removing it immediately breaks public traffic on that domain and can't be undone. | Before removing, update any links, QR codes or emails that use the domain. |
The list shows 20 hostnames at a time with Show more. With no domains registered it reads "No vanity domains configured." Only org admins can add or remove domains.
Removing a vanity domain takes effect immediately. Public pages served on that address stop working for visitors until you register it again.