Location-Level Overrides

What This Is

Many FSRevs features support both global settings (applied across all locations) and location-specific overrides — for example, Branding (logo, colors, layout) and Public Page Settings (featured reviews, local hours, display options). This page explains how the inheritance model works so you can predict what settings are in effect at any given location.

The Blank Box Rule

For branding fields and public-page fields that support inheritance:

Leave a local value unset to inherit its global default.

For display choices, use Inherit rather than Show or Hide. A saved local choice remains in effect even if you later change the global default.

Only the specific fields you change at the location level are overwritten — everything else keeps using the global defaults.

This rule does not apply to every empty field in FSRevs. Required location details still need values, and location-scoped Flows, Forms, or links are separate resources rather than replacements for global resources.

Why It Matters

Understanding inheritance prevents surprises. When a setting appears to “not work” at a specific location, it’s often because a global default is being overridden (or conversely, because a location-specific value hasn’t been set and the global default applies).

Features That Support Overrides

Feature	Global	Location behavior
Branding (logo, colors, layout)	Yes	Yes
Public page settings	Yes	Yes
Review flows	Available across locations	Location-scoped flows apply only there
Review sites / links	Global sites available at all locations	Location sites available only there
Smart links	Can be global	Can be location-specific
Custom forms	Can be global	Can be location-specific
Simple pages	Can be global	Can be location-specific

The first two rows inherit settings. The remaining rows describe availability. A local Flow or Form does not inherit the questions or configuration of a global one, and a local Smart Link does not automatically replace a global Smart Link.

How Overrides Are Indicated

In the portal, overridden and inherited settings are marked with visual cues:

Inherited from global — You’ll see text like “↑ Inherited from global” indicating the value is flowing through from your global settings
Overridden — A setting that has been explicitly set at the location level, replacing the global value
No global value — Shows that no default exists to inherit

These indicators reassure you that the flow-through logic is working as intended and help you understand when a field is still using the global setting versus when it’s been customized.

Practical Examples

Branding

Select Branding under Global Settings to edit Global Branding Defaults — Business-wide.
Open a location and select Branding Override to edit that location only.
You set a global logo and brand color → All locations without their own values use them.
You set a different logo for Location B → Location B uses its own logo while its blank branding fields continue inheriting global values.
You clear Location B’s logo and save → Only the logo falls back to the global value; its other overrides remain.

To remove just one branding override, clear only that field and save. This is different from resetting the complete location override.

The branding scope card and effective-value indicators show whether each result is local, inherited from global branding, or using a built-in default. Saving a location uses Save Location Override and never changes Global Branding Defaults.

Public Page Settings

Open Public Page Settings and use You are editing to choose the business-wide defaults or a location override.
Global changes use Save Global Defaults. Location changes use Save Location Changes.
At a location, leave a field unset to inherit it. For display choices, Inherit is different from explicitly choosing Show or Hide.
Reset to Global Defaults removes the current location’s complete Public Page Settings record; it does not change the global defaults or other locations.
Reset Global Defaults removes only the business-wide saved baseline and preserves location customizations. Reset All Public Page Settings is the separate action that removes both.

The editor warns before leaving or changing scope with unsaved changes. See Public Pages for the complete setup guide.

You add a global review link → It can be selected by compatible Review Flows across locations.
You add a Facebook review link scoped to Location A → It is available in Location A’s context, including a global Flow running there.
A Flow must still enable the desired review site. Adding a link to My Links alone does not guarantee that customers see it.

For a business with several Google listings, verify that each location’s customer experience opens its own listing. A global link to one branch is not a substitute for each branch’s review destination.

A global Review Flow can be used across locations.
A location-scoped Flow is limited to its own location.
A location-scoped Flow does not replace a global Flow with the same name. The selected request or Smart Link destination determines which Flow the customer opens; customers are not automatically shown a directory of every available Flow.

Comparison at a Glance

Feature	Global Setting (Parent)	Location Override (Child)
Branding	Main company logo	Branch-specific logo (overrides)
Public Page	Main company review page	Location-specific review page (overrides)
Show phone	Show the public-page phone	Hide the phone on one location’s page

These examples show that a location can keep most company-wide defaults while still customizing the few details that matter locally.

Common Mistakes

Expecting an overridden field to “stack” on its global value — A location value replaces that field, while unset fields continue inheriting
Not setting a global default — If neither scope has a value, the feature uses its built-in default or remains empty, depending on the setting
Forgetting which level you’re editing — Always check whether you’re editing global or a specific location’s settings
Treating Inherit and Hide as the same choice — Inherit follows future global changes; Hide is a saved local override