Getting Started

First-Run Setup

Before you can run paid events, you need to complete a few one-time org-level configuration steps. This page walks you through them in order.

Step 1: Verify the managed packages

  1. Go to Salesforce Setup > Installed Packages and confirm "Blackthorn | Events" (conference360__) is listed.
  2. If your org uses payments, confirm "Blackthorn | Payments" (bt_stripe__) is also installed.
  3. If the package is missing, contact Blackthorn support to obtain the installation link for your license tier.

Step 2: Assign permission sets

  1. In Salesforce Setup, go to Users > Permission Sets.
  2. Find the Blackthorn Events permission set (usually "Blackthorn Events Admin" or "Blackthorn Events User").
  3. Assign it to every user who needs access to Forge.

Permission sets control Forge access

Forge reads your Salesforce CRUD/FLS permissions at runtime. If a user cannot see a field in Salesforce, they cannot see or edit it in Forge. There is no separate Forge permission system — everything flows from Salesforce.

Step 3: Connect a payment gateway

  1. In Forge, open Admin (bottom of the sidebar).
  2. Navigate to Payment Gateways.
  3. Click "Add Gateway" and select your provider (Stripe, Authorize.Net, PayPal, or Spreedly).
  4. Enter your API credentials. These are stored in Salesforce as a bt_stripe__Payment_Gateway__c record — never in Forge's own database.
  5. Save and verify the connection with the "Test Connection" button.

Step 4: Configure org-level fee defaults (optional)

If you want to apply a default processing fee or service charge to all events, go to Admin > Fees and create a fee template. This creates a bt_stripe__Fee__c record that events can inherit. Individual events can override these defaults in their Tickets & Items tab.

Step 5: Set up email

Forge sends transactional emails (registration confirmations, tickets, reminders) through Salesforce's email infrastructure by default. If your org uses an external email provider (SendGrid, etc.), configure it in Admin > Communications.

You're ready

Once the packages are installed, permission sets are assigned, and a gateway is connected, you can create your first event. Head to the Quick Paths page for the fastest route to your first registration.