> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings hub

> Create reusable settings templates and apply them to multiple locations in your network.

## Overview

**Settings hub** lets you keep selected location settings consistent across a network. Create a template once, connect it to the locations that should receive it, and use it as the source for future changes.

Go to **Settings → Settings hub**. You need administrator access and access to the locations you want to manage.

## Before you start

* Decide which settings should be shared and which must remain local, such as a location's address or payment account.
* Ensure the destination locations already have any required features or integrations enabled.
* Start with a small group of locations and verify the result before applying a template more widely.

## Create a template

<Steps>
  <Step title="Open Settings hub">
    Select **Settings hub** from Settings.
  </Step>

  <Step title="Create a template">
    Choose to add a template and give it a name that explains its purpose, such as “Standard portal settings”.
  </Step>

  <Step title="Choose the settings">
    Add the location settings that the template should manage.
  </Step>

  <Step title="Connect locations">
    Associate the template with the locations or location network that should use it.
  </Step>

  <Step title="Review and apply">
    Confirm the selected locations, then apply the template and review each location's result.
  </Step>
</Steps>

## How templates work

Templates manage settings values, not every record belonging to a location. They are designed for repeatable configuration such as portal behavior, branding choices, or common operational settings.

When you update a template, use the hub to synchronise the revised values to its linked locations. The hub shows the locations connected to a template and records when its settings were last updated.

<Warning>
  Applying a template can replace existing values at a destination location. Check local exceptions before synchronising, particularly payment, access-control, and communication settings.
</Warning>

## Best practices

* Keep templates focused: use separate templates for portal settings, billing policy, and integrations.
* Use clear names that identify the affected locations and purpose.
* Maintain a short list of intentional local exceptions outside the template.
* Review a location after every template change, including its member portal where applicable.

## Related pages

* [Settings and configuration](/platform/settings/overview)
* [Languages](/platform/settings/languages)
* [Integrations](/platform/settings/integrations)