# Review customer intelligence settings

**Console: Settings → Business settings → Customer intelligence.** For the
restaurant owner and authorised setup lead. Confirm the business before
reviewing or changing these settings. They affect guest insight, not the staff
member's own menu of permissions.

## Understand the switches

| Setting                                       | Meaning in the current interface                                                                   |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Build guest profiles                          | Keeps recorded visit count, spend, value and cadence information current after successful payments |
| Show the insights dashboard                   | Enables the customer brief; the interface requires guest-profile building first                    |
| Recognise consenting guests across businesses | Enables the restaurant-side recognition setting; guest consent remains a separate requirement      |

A setting being on does not prove sufficient history, complete guest identity,
or that every visit is linked. Do not promise instant, complete historical
profiles after enabling it. Check [Members](/customers/members) and the actual
[Customer brief](/customers/insights).

The cross-business setting does not grant staff access to another business's
member records or authorise sharing records between separate companies. Do not
infer consent from a payment, member profile, common ownership, or a restaurant
switch. Review the actual guest consent and supported recognition outcome.

## Change and verify deliberately

The page can show **Administrator access required** and read-only switches for
restaurant operators. Use the authorised setup/support path when changes are
needed; do not obtain broader access merely to match the guide.

Where changes are available, review the intended switches, then save and reopen
the page. Turning off **Build guest profiles** also clears the dashboard switch
in the form; verify both saved values. Discarding an unsaved form does not
reverse an earlier saved change.

Turning a feature off is not proof that existing profiles were deleted, all
connected clients lost access, or unrelated marketing settings changed. Check
the supported record/access workflow for those separate requests.

## Missing or unexpected insight

**Insights are switched off** is a settings state, not a failed data query.
After the authorised settings are saved, inspect real profile activity and the
brief. A **Sample preview** is illustrative; its names and figures are not
restaurant evidence. Missing recognised history can reflect incomplete records,
linking, consent, or feature availability rather than no prior visit.

After an uncertain save, inspect the same business's settings before repeating
it. Escalate with business, intended/saved switches, relevant profile or brief
state, and exact error through an authorised channel. Keep guest identity and
payment information out of public captures and assistant prompts.