Sign in

Beta & Experimental Features

Advanced Visibility

Early AccessManage on the Beta Features page

Advanced Visibility is a rules engine that controls who can see and register for an event, or for specific items and sessions within it. A rule is a set of conditions on the Salesforce Contact (or Person Account). When someone opens your event in an Experience Cloud site or an embedded flow, Forge shows the event, item or session only if that person's Contact matches the rule attached to it.

Availability

Advanced Visibility is GA but off by default. An admin turns it on from the Beta features page (/beta). It also needs Advanced Visibility to be enabled for your Salesforce org; if it is not, the page tells you to ask your Blackthorn admin to enable it before you can create or edit rules.

Availability

Advanced Visibility is GA but off by default. An admin turns it on from the Beta features page (/beta). It also needs Advanced Visibility to be enabled for your Salesforce org; if it is not, the page tells you to ask your Blackthorn admin to enable it before you can create or edit rules.

Where to find it

Open an event, then Visibility. The page is titled Advanced Visibility. A What is Advanced Visibility? panel explains the idea and links to the Advanced Visibility guide. Two badges show how many rules exist (Rules) and the current Attach scope.

Create or edit a rule

  1. Choose Create New Rule (or Edit Rule on an existing one).
  2. Fill in the rule fields below.
  3. Add one or more conditions.
  4. Choose Create Rule, or Save Changes when editing.
  5. Attach the rule to the event, to items, or to sessions (see Apply a rule).
FieldWhat it doesRecommendation
NameThe rule's name, shown in the picker and the rules table. Required.Name it for who it admits, such as Gold members only.
ActiveRule will not be evaluated when it is not active. Only active rules can be added to other records.Leave Yes. Use No to retire a rule without deleting it. Attaching an inactive rule asks you to confirm because it has no effect until activated.
Condition typeHow conditions combine: AND (all conditions), OR (any condition), or Custom logic is met.Use AND to require everything, OR to admit anyone who matches at least one, Custom for mixed logic.
Custom logicShown for Custom. Reference each condition by its order number and combine with AND, OR and parentheses, such as (1 AND 2) OR 3.Every condition must appear in the expression. You are told if one is missing or refers to a condition that does not exist.
Extend Visibility to AccountEach contact is evaluated on their own. When Yes, if one contact in an account matches, every contact in that account gets access. For Experience Cloud sites only.Use Yes for household or company access, where one qualifying person should open the event to colleagues. Leave No when access is strictly personal.
Extend Eligibility to AccountThe same idea for registering rather than viewing: when one contact in the account is eligible for an item, all contacts in the account are.Turn on when one eligible buyer can register on behalf of the account.
DescriptionFree-text note about the rule's intent.Say why the rule exists so the next admin does not have to guess.

Conditions

Each condition has a Field (a Contact field), an Operator and a Value. Add Condition adds a row; Remove condition deletes one. A rule can have at most 25 conditions. Changing the field clears the operator and value. Field, operator and value are all required.

Field typeOperators offeredNotes
CheckboxEQUALS, NOT EQUAL TOValue is True or False.
Text, phone, email, URL, picklist, lookupEQUALS, NOT EQUAL TO, GREATER THAN, LESS THAN, GREATER OR EQUAL, LESS OR EQUAL, CONTAINS, DOES NOT CONTAIN, STARTS WITHCONTAINS and DOES NOT CONTAIN take several values at once.
Number, currency, percent, date, date and time, timeEQUALS, NOT EQUAL TO, GREATER THAN, LESS THAN, GREATER OR EQUAL, LESS OR EQUALPick a value of the matching type.
Multi-select picklistEQUALS, NOT EQUAL TO, INCLUDES, EXCLUDESINCLUDES and EXCLUDES take several values.

To admit contacts who have a membership level of Gold or Platinum, use one condition: Membership Level, CONTAINS, with both values selected. To require Gold and a paid status, add two conditions and use AND.

Apply a rule

ControlWhat it doesRecommendation
RuleThe rule to attach.Only active rules are good choices.
Apply ToThe scope: Event, Event Items or Sessions. Items and Sessions open a table to tick the records to target (sessions are grouped by day, with an Unscheduled group). Refresh reloads the list.Attach to the event to gate the whole event, to an item to gate one ticket type, and to a session to gate one session.
AttachAttaches the rule to the selected record(s). The result shows how many attached and how many failed.If a record already has a different rule you are asked to confirm Replace rule.
DetachRemoves the rule from the selected record(s).Use to stop a rule applying to a record.
Current rule columnFor items and sessions, shows the rule already on each row.Check it before replacing.

Where this rule applies, when editing a rule, lists every event, event item and session the rule is attached to (Events, Event Items and Sessions tabs). If it is attached to nothing it says Not attached to anything.

Visibility Control: the simpler option

Visibility Control is a lighter mechanism that works alongside rules. Under Visibility Control, pick one or more values and choose Apply for the event, items or sessions in the current Apply To scope. A record shows to a contact whose own Visibility Control field has a matching value. The values are the options configured on the Visibility Control field in Salesforce, for example Member or Non-Member; if none are configured you see a message saying so.

ApproachUse it when
Visibility ControlOne simple label on the contact decides access, such as Member versus Non-Member.
Advanced Visibility ruleAccess depends on several Contact fields combined with AND, OR or custom logic, or should extend to everyone in an account.

Existing rules

The table lists Name, Active, Type, Attached, Conditions and Description for every rule. Preview records opens the Visibility Rule Preview, which shows which contacts a rule would currently match; it is a separate feature that must be on for your organization. Deleting a rule asks you to confirm and tells you how many events, items and sessions it will be cleared from.

Deleting a rule

Deleting a rule clears it from every event, item and session it is attached to. Check Where this rule applies first, and detach or replace the rule if you do not want that.

Check a new rule before you rely on it: if Visibility Rule Preview is on for your organization, use Preview records to see which contacts it matches, and attach it to one test session first.