Vendion
    Chain Operations

    Chain Settings – Feature Toggles

    5 min read#15

    Chain Settings is the control room for the chain owner. Here you toggle the four sharing flags controlling which features are active in the chain, and configure intercompany accounts for bookkeeping.

    Where to find it

    /chain/:slug/installningar in the chain console. Page visible to all chain admins with the right to manage chain settings (in MVP: all Admin group members).

    Basic info (mostly read-only)

    At top of the page:

    FieldEditable?
    NameYes (editable by chain admin)
    SlugNo (contact Vendion support to change)
    TypeNo (read-only badge: franchise/holding/custom)
    OwnerNo (contact Vendion support to change owner)
    CreatedNo (historical date)

    The four sharing flags

    Main part of the page. Each flag has toggle and description:

    1. Central menu management

    • Desc: "Chain admin builds templates published out. Local admins can override unlocked fields."
    • When ON: Menu template page visible in nav; publishing available
    • When OFF: menu template pages hidden; existing local copies preserved unchanged

    2. Brand control

    • Desc: "Lock logo, colors, fonts, and online order AI personality."
    • When ON: Brand page visible; field locks applicable to all restaurants
    • When OFF: existing field locks preserved but can't be changed centrally

    3. Shared loyalty

    • Desc: "Points and stamp cards shared across chain restaurants. Migration on activation."
    • When ON (planned): Loyalty page visible; pooled loyalty activated; migration job triggered
    • When OFF: local loyalty continues per restaurant
    • Note: Feature planned Q2-Q3 2026; flag can be enabled now but no direct effect yet

    4. Shared gift cards

    • Desc: "Cards sold at one restaurant redeemed at another. Intercompany when org numbers differ."
    • When ON: POS shows "Valid across chain" toggle; cards can be sold with chain scope; intercompany logged
    • When OFF: only local gift cards; existing chain cards keep scope but new ones aren't created

    Type presets

    When a chain is created, flags are set per type:

    TypeMenuBrandLoyaltyGift cards
    Franchise
    Holding
    Custom

    You can always change flags after creation.

    Save flow

    On flag change:

    1. Toggle → value changes
    2. Click "Save"
    3. Chain settings updated
    4. Permission check: only Vendion admin or chain admin with the right to manage chain settings is allowed to save
    5. UI refreshes, navigation menus update (new pages appear/disappear)

    Intercompany accounts (BAS)

    Below flags, a section for accounting accounts:

    FieldDefaultUse
    Receivable account1660Receivable from group companies
    Payable account2860Payable to group companies

    Used when auto-generated intercompany vouchers are created in Z-report. Customizable if your bookkeeper prefers other BAS accounts.

    Note: Changes only apply to future vouchers – already-settled vouchers keep their original accounts. So only change at start or after consultation with bookkeeper.

    Danger zone: terminate chain

    In future versions, a "Terminate chain" button will appear on this page. In MVP, contact Vendion support to terminate a chain.

    Effect of post-launch flag changes

    Scenario 1: Chain created as franchise with full sharing. Alice wants to disable central menu management:

    1. Toggle OFF → Save
    2. Menu template page disappears from nav
    3. Existing local copies preserved as-is
    4. Local admins can now freely edit (field locks preserved but no new publishes)
    5. If Alice turns ON again later: template still exists, can be published again

    Scenario 2: Chain was "custom" without gift cards. Alice wants to activate:

    1. Toggle shared gift cards ON → Save
    2. Chain gift cards page appears in navigation
    3. POS at all units gets "Valid across chain" toggle
    4. Existing local gift cards keep their scope (local) – only new ones can be chain cards

    No irreversible effects on toggle.

    Security behind the flags

    Flags control more than the UI – they also affect permissions at the database level:

    • If central menu management is OFF: the chain menu template isn't accessible to chain admins
    • If brand control is OFF: chain brand settings can't be updated
    • If shared loyalty is OFF: chain loyalty data is blocked

    All checks happen directly in the database, not just in the app. Attempts to bypass the UI via direct API calls fail.

    Audit log (future)

    All chain settings changes logged for traceability. Question "who turned off loyalty on 2026-06-15?" should be answerable. MVP: log exists but no UI yet.

    Who sees the page?

    • Chain owner: always
    • Chain member in Admin group: yes (has full access)
    • Future custom groups: can be restricted so some admins only see settings but can't change
    • Local restaurant admins: do NOT see this page (not even via capability inheritance)

    Best practice

    We recommend:

    • Set flags at chain creation and change rarely after
    • Invite a second admin before big flag changes (safety)
    • Document changes externally (audit log UI coming later)
    • Turn off carefully – local admins may get confused if functionality suddenly disappears

    Next step: Read Chain Owner's Console to understand what features you have access to.

    This feature is part of Vendion Chain Operations.

    Curious how it looks in practice? Read more about the product or book a short demo.

    Was this article helpful?