Location-Level Overrides
What This Is
Section titled “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
Section titled “The Blank Box Rule”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.
Why It Matters
Section titled “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
Section titled “Features That Support Overrides”| 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 |
How Overrides Are Indicated
Section titled “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
Section titled “Practical Examples”Branding
Section titled “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
Section titled “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.
Review and Social Sites
Section titled “Review and Social Sites”- 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
Review and Social Flows
Section titled “Review and Social Flows”- 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
Comparison at a Glance
Section titled “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) |
| 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.
Common Mistakes
Section titled “Common Mistakes”- Expecting an overridden field to “stack” on its global value — A location value replaces that field, while blank fields continue inheriting (review sites merge separately)
- 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