Skip to content

Location-Level Overrides

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 easiest way to think about settings is:

If you leave it blank, it stays Global.

Values from your Global Settings (the parent) flow through to every location automatically. They’ll continue to flow through unless you explicitly enter something different for a specific location.

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

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).

Feature Global Location Override
Branding (logo, colors, layout) Yes Yes
Public page settings Yes Yes
Review flows Global flows apply everywhere 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

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.

  • You set a global logo and brand color → All locations use them
  • You set a different logo for Location B → Location B uses its own logo, all others use the global one
  • You remove Location B’s logo override → Location B falls back to the global logo
  • You add Google Reviews as a global review site → Available in all flows at all locations
  • You add a Facebook review link scoped to Location A → Only Location A flows can show Facebook
  • Review flows at Location A see both Google (global) and Facebook (location); Location B sees only Google
  • A global review flow is accessible from any location
  • A location-scoped flow is only accessible from that location
  • If a customer selects Location A, they see global flows AND Location A’s flows
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)
Phone Company headquarters number Branch direct line (overrides)

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

  • Expecting a location override to “stack” on global — Overrides replace the global value, they don’t add to it (except review sites, which merge)
  • Not setting a global default — If no global value exists and no location override exists, the setting is empty
  • Forgetting which level you’re editing — Always check whether you’re editing global or a specific location’s settings