Sign in

Core Concepts

Permissions

Access in Forge has two layers, and both apply at all times. Salesforce decides what data someone can read and write: profile, Blackthorn permission sets, field-level security and sharing rules. A Forge role (Admin, Planner or Custom) then decides which Forge pages the person can open. Neither layer replaces the other.

QuestionAnswered byWhere to change it
Can this person open the Admin pages?Their Forge role (Admin)Admin > Users; or the Salesforce permissions that make them an Admin
Can they see this event, attendee or transaction at all?Salesforce sharing rules and object permissionsSalesforce Setup
Can they see or edit this field?Salesforce field-level security (FLS)Salesforce Setup > Permission Sets or Profiles
Can they see this sidebar item or event page?Forge Custom profile (Read, Write or blank), for Custom usersAdmin > Profiles (Blackthorn-managed today)
Can they charge or refund a payment?The Blackthorn Payments permission sets in Salesforce, plus payment tools being enabled for the orgSalesforce Setup

How Salesforce permissions flow into Forge

Every request Forge makes to Salesforce uses the signed-in person's own Salesforce session. Salesforce enforces object permissions and field-level security on each operation, so Forge cannot show or change anything the person could not in Salesforce itself.

Blackthorn permission sets

Blackthorn provides managed permission sets that grant the minimum access to the package objects:

  • Blackthorn Events Admin — full CRUD on all conference360__ objects. Intended for event administrators and Salesforce Admins.
  • Blackthorn Event Organizer — day-to-day event management access. This is the standard planner-level Events set.
  • Blackthorn Events Lite User / Blackthorn Events Limited Access — narrower Events access for occasional or restricted users.
  • Blackthorn Events Read Only — view-only access to Events data.
  • Blackthorn Base Admin / Blackthorn Base User / Blackthorn Base Read Only — access to the Base package objects underlying core record access.
  • Blackthorn Payments Admin — full CRUD on bt_stripe__ objects. Required for gateway configuration and refund processing.
  • Blackthorn Payments User / Blackthorn Payments Manager — read and day-to-day transaction/fee access without gateway or refund rights.
  • Blackthorn Payments Lite User — narrower, view-oriented Payments access.

A Salesforce admin assigns Blackthorn permission sets in Setup > Users > Permission Set Assignments. Do this before the person first signs in to Forge. Forge roles are separate and are shown in Admin > Users.

How Forge roles relate to permission sets

Forge does not set a role from a named permission set. At sign-in it reads the person's real Salesforce permissions: if any profile or permission set grants Modify All Data, Manage Users or Customize Application, the person is an Admin, otherwise a Planner. An Admin can change a role by hand, and a hand-set role is not overwritten later. Custom is only ever assigned by an Admin. See Roles & Access.

Forge roleTypical Salesforce permission setsWhat the user can do
AdminBlackthorn Events Admin, Blackthorn Base Admin, and Blackthorn Payments Admin if they manage gateways or refundsEverything Salesforce allows, plus the Forge Admin section.
PlannerBlackthorn Event Organizer (plus Base User and Payments User as needed)Create and manage events, attendees, sessions, forms and communications; no Admin section.
Planner (limited)Blackthorn Events Lite User, Limited Access or Read OnlyOnly the records those permission sets expose, even though the Forge role is Planner.

A user with the Forge Admin role but no Payments Admin permission set can open the Payment Gateways page, but Salesforce refuses gateway changes. Assign the Salesforce permission set first, then the Forge role.

Field-level security in practice

What you seeWhat it meansWhat to do
A field is missingSalesforce says you cannot read it. Forge hides it in screens and in exports.Ask your Salesforce admin to grant read access on that field.
A field is greyed out or you see You don't have permission to edit <fields>. Contact your Salesforce admin.You can read it but not edit it.Ask for edit access, or ask someone who has it.
Couldn't verify field permissions - please try again.Forge could not check your access this moment.Retry in a moment.
Changed a permission set but nothing changedForge caches field access for about a minute.Wait a minute and reload.

Sharing rules and record access

If your org's organization-wide defaults or sharing rules restrict conference360__ records, those limits carry through. A person only sees events, attendees and transactions that Salesforce lets them see. Lists that come from Salesforce list views follow the same rules.

Edit locks

When someone is editing a record in Forge, another person who opens it is told This record is being edited by <name>. A lock that expires shows Your editing lock expired - please refresh and try again. This is a Forge courtesy to prevent overwrites; it is not a permission.

Admin-only features in Forge

  • The whole Admin section, and Global Options.
  • Payment gateway configuration (also needs the Blackthorn Payments Admin permission set).
  • Beta features: switching optional features on for the org.
  • Email sender and domain settings.
  • Org-wide switches such as Disable Communications and Disable Audiences.
  • The Admin logs.