Getting Started
First-Run Setup
Before the first event, an Admin completes a few one-time steps. Steps 1 and 2 apply to every org. Step 3 (email) is needed before Forge can send any email. Step 4 (payments) is only needed for paid tickets. The Setup page (Admin > Setup, also the Setup card on Home) tracks your progress and links to each fix.
Fastest route: open Admin > Setup and work top to bottom. Green means done and amber means action needed. The required steps are Salesforce connected, required apps installed, email domain verified and a default From address set.
The setup checklist
| Step | Required? | What it checks | How to fix it |
|---|---|---|---|
| Salesforce Connected | Required | The org is connected through OAuth. Shows the org name and whether it is Sandbox or Production. | Done when you first sign in. If the connection later expires, choose Reconnect in the banner or use Admin > Salesforce Org Connection. |
| Required Apps | Required (once the package scan has run) | That Blackthorn Events (conference360__), Blackthorn Base (bt_base__) and Blackthorn Payments (bt_stripe__) are all installed. Payments is needed even for free events. | Have your Salesforce admin install the missing package, then rescan under Admin > Salesforce Org Connection > Installed packages. |
| Users & Permissions | Optional | Counts as complete once more than one user exists. People appear when they first sign in. | Ask teammates to sign in. Assign roles in Admin > Users. |
| Email Domain | Required | That your sending domain is verified. DNS changes can take 24 to 48 hours. | Admin > Email Settings & Preferences: add the sending domain, create the DNS records and choose Verify. |
| From Address | Required | That a default From address is set. It is required before any email is sent. | Admin > Email Settings & Preferences. |
| Payment Gateway | Optional (needed for paid events) | That a payment provider is connected. | Admin > Payment Gateways. |
| Package Versions | Optional | Whether the installed Blackthorn packages were scanned, and how many features that unlocks. | Choose Scan installed packages on the Salesforce Org Connection page. |
Step 1: Verify the Blackthorn packages
- In Salesforce Setup, open Installed Packages and confirm Blackthorn Events (conference360__), Blackthorn Base (bt_base__) and Blackthorn Payments (bt_stripe__) are listed — all three are required for Forge.
- If one is missing, contact Blackthorn support for the installation link for your license tier.
- A new org can only connect with Blackthorn Events 5.44.0 or newer.
Step 2: Assign licenses and permission sets in Salesforce
- Assign the managed-package license to each user (Setup > Installed Packages > Manage Licenses) for Events, Base and Payments, unless a package is licensed as a site license.
- In Setup > Permission Sets, assign a Blackthorn Events set to each person who needs Forge: Blackthorn Events Admin for full access, or Blackthorn Event Organizer for everyday event management.
- Also assign a Blackthorn Base set, and a Blackthorn Payments set to anyone who configures gateways or processes refunds.
Forge reads each person's Salesforce permissions at runtime, so a field or object hidden from someone in Salesforce is hidden from them in Forge. A Forge role (Admin, Planner or Custom) is a second layer on top: Modify All Data, Manage Users or Customize Application in Salesforce makes someone an Admin when they sign in; everyone else is a Planner. See Roles & Access.
If a regular user sees Your Salesforce admin needs to finish setting up Forge on sign-in, a Salesforce admin must open the Blackthorn Forge connected app and allow all users or the right profiles. Steps are on Log In and Connect Salesforce.
Step 3: Set up email
Forge sends its own email through a sending account created for your org. It does not use Salesforce org-wide email addresses. Do this before launching an event, because confirmations are email.
- Open Admin > Email Settings & Preferences.
- Enter a From name and From address on a domain you own.
- Register your sending domain, add the DNS records at your DNS provider and choose Verify DNS.
- Send a test email to confirm.
If you use Marketing Cloud, you can skip this step. Otherwise make sure the same message is not also sent from Salesforce, so people do not receive duplicates. The Disable Communications switch on the Admin page hides the Communications tabs if you send from another system.
Step 4: Connect a payment gateway (paid events only)
- Open Admin > Payment Gateways.
- Choose your provider and enter its credentials. Forge supports Stripe, Authorize.net, TouchNet and other providers through Spreedly. CashNet can be connected, but Forge cannot charge through it yet.
- Save and confirm the connection shows as Connected on Setup.
Gateway records are stored in Salesforce, not in Forge. Connecting a gateway needs the Blackthorn Payments Admin permission set.
Fees such as processing and tax are set on events and tickets, not in a global fee template: see Tickets and Items. Skip this step when you only run free events.
You're ready
Once the required steps are green, create your first event. Quick Paths has the fastest routes.