concept · explanation

Configuration inheritance

Understand how configuration inheritance works in Slash Social.

Slash Social stores settings in layers. More specific layers override broader defaults without copying the entire configuration each time you save a change.

Overview

Configuration answers “what should this brand do by default?” for cadence, voice, links, review labels, and dozens of other domains. Instead of one flat settings file per brand, the product resolves effective settings by walking a scope chain from global defaults down to the narrowest scope you set. You change only the layer where a difference matters; everything else keeps inheriting.

Admins edit settings from the Settings work center in /social. Forms show an effective summary for the scope you pick before you submit.

How it works

Settings resolve in this order, from broadest to narrowest:

  1. Global defaults ship with the product (posting windows, platform capabilities, review labels, and similar baselines).
  2. Organization overrides apply to every brand in the org.
  3. Brand overrides express voice, cadence, and learning preferences for one content identity.
  4. Campaign, pillar, platform, and account overrides tune a launch, content theme, network, or connected profile.

When the product reads effective settings for a post, the narrowest scope you set wins for each field. You do not repeat unchanged fields at every layer.

Merge behavior follows three rules:

  • Objects merge field by field. If the brand sets a Saturday posting window and the global default defines Monday through Friday, both apply.
  • Arrays replace entirely at the scope where you save them. Saving a new list of posting windows at brand scope replaces the inherited list for that scope; it does not append to the global list.
  • Primitives (text, numbers, booleans) override outright at the saving scope.

Configuration is grouped by domain. Typical domains include cadence (posting windows and quiet hours), cta (link and bio defaults), learning (AI bandit and recipe settings), platforms (format and capability toggles), branding (voice and tone), review reasons, utm, and daily feed settings. The Configuration domains reference lists the full set.

Cadence and CTA settings usually start at brand scope. Platform capability overrides often target a single network name. Account scope is for profile-specific timezone or window tweaks.

Changes save immediately when you submit a config form. Some Slack views may take a few minutes to reflect updates.

You reach domain forms from the Settings hub or the config picker described in Edit configuration forms. Campaign and pillar scoped forms appear when you manage those objects and need overrides tighter than brand defaults.

Examples

Your org keeps global weekday posting windows. One brand adds Saturday hours at brand scope. Posts for that brand inherit Monday through Friday from global defaults plus Saturday from the brand override.

A campaign needs a different call-to-action link for two weeks. You set a cta override at campaign scope. When the campaign ends, remove the override and posts fall back to brand and org defaults.

An Instagram account posts in a different timezone than the brand default. You set an account-scoped cadence tweak for that profile only. Other accounts on the brand keep the brand windows.

Review reason labels inherit from global defaults. An org adds a custom rejection label at org scope; every brand sees it unless a brand replaces the review reasons array entirely at brand scope.