Sign in

Admin

Salesforce Org Connection

The Salesforce Org Connection page (Admin > Org, at /admin/org or /org) shows the Salesforce org Forge is connected to and is where you repair the connection, refresh what Forge knows about the org, and check that Blackthorn packages and Registration Sync are healthy. Org Data and Org Layouts are read-only companion views.

Connection details

When connected, four read-only fields describe the link.

FieldWhat it showsRecommendation
Org IdThe Salesforce organization ID of the connected org.Compare it with the org you intended. If you meant to connect Production but see a Sandbox, reconnect.
UsernameThe Salesforce user whose credentials Forge is using for the connection.Prefer a dedicated integration user with the permissions Forge needs, so the connection does not break when a person leaves or changes password.
Instance URLThe Salesforce server address the org lives on.Use it to confirm Production versus Sandbox.
API VersionThe Salesforce API version Forge calls.Informational. You do not set it here.

If the org is not connected, the page says "Not connected to Salesforce" and offers Open OAuth setup. Click it, choose your login host (Production, Sandbox or My Domain), sign in, and you return to this page when the handshake finishes.

Buttons

ButtonWhat it doesWhen to use it
Reconnect to SalesforceSigns in to Salesforce again. For an admin this is a full disconnect-and-reconnect: Forge clears the stored org-level connection and its cached connection state, then restarts sign-in. A non-admin only re-signs-in for their own user.Use when Forge reports it lost access, a Salesforce session or refresh token expired, or someone changed the connected user's password, IP restrictions or connected-app policy.
Refresh metadataReloads the org's metadata (objects and fields) into Forge.Use after an admin adds or changes a custom field, picklist value or object in Salesforce and you want Forge to see it right away.
Clear connection errorAppears for admins only when a connection error is stored. After confirmation it clears the stored error so you can retry. You still need to reconnect Salesforce.Use after fixing the cause of the error (for example allowing Forge's IP), then reconnect.
Disconnect OrgAdmins only. After confirmation, removes the Salesforce connection for your account, signs you out, and you must authenticate again to reconnect.Use only when you intend to point Forge at a different org or retire the connection. For ordinary problems use Reconnect instead.
EditShown only in a demo org to company admins; opens the page in edit mode (/org?edit=1). Demo orgs are otherwise read-only.Not relevant to customer orgs.

If reconnecting fails

If Salesforce hands Forge a token but rejects the first verification call, a red banner reads "Salesforce rejected the new connection". It means the connected app, an IP allowlist or the user's permissions blocked access. The banner may also show the last error code and when it happened.

  • Try connecting again (admins get a full disconnect-and-reconnect) restarts the sign-in.
  • Contact support emails Blackthorn support.
  • If the banner says the saved Salesforce credentials cannot be read, an admin needs to choose Reconnect Salesforce in the banner; if it says the app settings are incomplete, contact support.

To fix a rejected connection, ask your Salesforce admin to check the three things the banner names: the connected app's access policy for that user, any IP allowlist that could block Forge, and the user's permissions. Then clear the connection error here and reconnect.

Registration Sync

Registration Sync keeps Forge up to date when registrations change inside Salesforce (a registration, cancellation, session attendance, waitlist promotion, check-in or capacity update). It works by deploying a small configuration into your Salesforce org. This card appears on the org page for users who are not on a custom role.

ItemWhat it meansRecommendation
Registration Sync is not enabledNothing has been deployed yet, so registrations made in Salesforce will not update Forge. Admins see Enable Salesforce Sync, which deploys the configuration to your org automatically. Non-admins are told to ask a user with the Admin role.Enable it once after connecting. The Salesforce user connecting needs the Customize Application or Modify Metadata permission.
Active / Stale badgeActive means the deployed configuration matches this Forge. Stale means the endpoint URL or the worker token stored in Salesforce no longer matches this Forge instance.If Stale, an admin clicks Re-provision (or Rotate Token when only the token changed) to rewrite the Salesforce configuration.
Endpoint, Worker Token, Named Credential, Email TemplateRead-only details of what was deployed. The worker token is masked. Email Template says Sync-only (no template) when no template is attached.Normally nothing to change. They help support troubleshoot.
Deployed at and last provision errorWhen the configuration was deployed and, for admins, the last error if provisioning failed.Fix the error (typically permissions, an expired Salesforce session, or the daily API limit) and click Re-provision.
Recent ActivityThe latest sync events, such as Registration, Cancellation, Session attendance, Waitlist promotion, Check-in, Capacity update, and how many attendees each affected.Use it to confirm that a change made in Salesforce has reached Forge.
Supported / Upgrade requiredBlackthorn Events must be at the minimum version Forge needs to track registrations. The card shows the installed and required versions.If Upgrade required, update the Blackthorn Events package in Salesforce.

Under the card, a one-line status reports whether Forge is actually receiving Salesforce events: listening (with the time of the last event), off (terms not yet accepted, or not enabled for the org), or not receiving, with the reason: the connected user lacks Read access to the registration platform events, Salesforce needs reconnecting, the org's daily platform event allowance is used up, the Forge worker has not checked in for over 15 minutes, or a connection error is being retried.

Installed Packages

Lists the managed packages Forge detected in the org, with Namespace, Package and Version. Click Scan packages to refresh the list; the Last scanned time is shown underneath. If the Blackthorn Events package is older than Registration Sync requires, an amber banner reads "Update Blackthorn Events to Enable Registration Sync" with the installed and required versions.

Setup uses this scan to decide whether the Events, Base and Payments apps are all installed. If a package you just installed does not show up, run Scan packages.

Object mapping

Mapping Forge's concepts (Event, Ticket and so on) to the matching Salesforce objects is covered on the Object Mapping guide page. Mappings are limited to Blackthorn Events, Base and Payments objects.

Org Data (read-only)

Org Data lists records Forge has cached from Salesforce, up to 25 per list: Events, Event Groups, Sessions, Tickets, Invoices, Transactions, Forms, Form Elements, Registrations, Tables, Seats and Codes. A list is only available if the matching object is mapped for your org. Refresh Cache reloads them, a Synced timestamp shows freshness, and a Stale badge appears when the cache is out of date. Connect your org on the Org page first.

Use Org Data to check whether a record you just created in Salesforce has reached Forge. If it is missing, click Refresh Cache; if it is still missing, check Registration Sync and Salesforce writes.

Org Layouts (preview)

Org Layouts previews how Salesforce page layouts are rendered in Forge, so you can see why a field is or is not shown. Select an Object and then a Record Type (when the object has several) to inspect the layout.

ItemWhat it shows
Layout sourceWhere the layout came from: Record type layout, Record type mapping or Default layout.
Active record type, Active layout id, Mapping sourceWhich record type and layout Forge picked for that object, and how.
Sections and fieldsEach section's heading, its row and column count and the fields in it, with badges: Required, Custom, Layout, Read-only. Picklist fields show how many values they have and whether they are Dependent.
Missing describe metadataA warning that lists fields whose metadata Forge does not have yet. They may be new; click Refresh metadata on the Org page.

These views read from Salesforce. Changing a layout or a field still happens in Salesforce; use Refresh metadata afterwards.

Org connection settings are for org admins.