Skip to content

System mode

By default a badge appears only for users who can read its source records, as described in What a viewer sees. Sometimes a badge should show regardless: an "Open case" badge on a contact that the support team should see even when they have no access to cases, or a "VIP" badge driven by a field most users cannot read. System Mode does that for a single badge definition.

What System Mode does

When System Mode is checked on a Highlight Badge Definition, its badge is shown to every user who can see the page, whatever their object, field and sharing access to the source records. The badge query runs with the package's own access, so:

  • the badge appears even when the user cannot read the source object, the records, the fields in the Filter Criteria or Order By, or the fields on the relationship paths
  • merge fields in the Badge Label and Alert Message are filled in for everyone who sees the badge

The definition itself is still read as the running user, so the user needs the Highlight Badges Viewer permission set (or equivalent) as before.

What users see

Users who could read the source record anyway see the badge exactly as they would without System Mode.

Users who cannot read the source record see the badge, its label and its alert, but not the record:

  • the details modal shows "You don't have access to this Object's details." instead of the record's fields
  • a Source Record navigation action is left out of the badge's actions
  • a toast alert carries no link to the record

Web Page navigation actions and Flow actions still run. Flows receive the source record ID as an input if the action passes it, and run with their own access.

Users who can read the record but not every one of its Source Detail Fields see the fields they can read, as on any other badge: detail fields are read through Lightning Data Service, which respects field-level security.

Turning System Mode on

Only users with the Can Enable System Mode custom permission can change the checkbox. Highlight Badges Admin and Highlight Badges Starter Packs Admin grant it; see User security. Without the permission, saving a definition with System Mode checked fails with a validation message, including when the record is new or cloned. A user without the permission can still edit the other fields of a definition that is already in System Mode.

To turn it on:

  1. Open the Highlight Badge Definition.
  2. In the Visibility & Access section, check System Mode and save.

Note

Orgs that installed Highlight Badges before version 1.12 keep their existing page layout. If the Visibility & Access section does not show System Mode, add the field to the Highlight Badge Definition page layout under Setup → Object Manager → Highlight Badge Definition → Page Layouts.

Guest users

System Mode can be combined with Visible to Guest Users to show a badge on a public Experience Cloud page.

Public data

A system-mode badge that is visible to guest users shows its label, its alert message and any merge-field values to anyone who can open the page, logged in or not. Use only fields that may be public, and keep Source Detail Fields to what a guest may see. Guests never get the record's details or a link to it, since a guest cannot read the record.

See Page contexts for the visibility checkboxes.

Starter packs

Starter packs do not carry System Mode. A definition imported from a starter pack arrives with System Mode unchecked, so a pack can never turn it on in your org without an admin's say-so.