# Saving settings

Save website settings while checking for newer changes and updating connected operators.

*Release 3.3 · admin, developer, supervisor*

**General Settings** · **Account**

## What it is

INSIDE checks the version of website settings loaded in your console when you save. This helps detect changes made since you opened them. Saved changes are sent to connected operators so their consoles can use the updated configuration.

## Who uses it and why

Users with the **Settings** role save changes through the settings screens delegated to them. Powerfront changes Powerfront-managed settings on your behalf. Developers should use the supported integration documentation for any automated configuration work.

## Where to find it

Use **Save** in the relevant settings screen, such as **Settings › General Settings › Website**. There is no separate revision editor to configure.

## How it works

1. Open the required screen in the correct website account.
2. Make your changes and choose **Save**.
3. If the save is rejected after someone else has changed settings, reload the current settings and reapply your intended changes.
4. Reopen the screen to verify the saved values.

Settings updates are sent to connected consoles. Updated groups of options replace the previous group, so options removed by the change should disappear there too. Settings changes can also create operator activity records.

## Configure it

There is no client-configurable revision number or live-update switch. Use the ordinary settings screens and their **Save** actions. Permission to edit client-managed screens can be delegated through the operator's **Settings** role. Ask Powerfront to change Powerfront-managed settings.

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Save website settings, subject to the screen and field permissions. |
| Powerfront | Change Powerfront-managed settings on your behalf. |

## Limits and good to know

Saving requires a current settings revision and appropriate access. An outdated console may need to reload before another save succeeds.

A screen can save account details, settings and enablement choices separately. A visible update or success message does not guarantee that every part of a multi-part change has completed. Reopen the screen when verifying an important change.

This release does not provide a general settings undo or restore-to-revision screen.

## Depends on and works with

### This feature uses

- **Configured in** [Switching between websites](ADM-002.md): The website selected in the directory determines which account receives a settings change.
- **Configured in** [Roles and permissions](ADM-008.md): Roles and delegated permissions govern settings access.
- **Related** [Operator Log](REP-022.md): Review operator activity history to investigate recorded settings changes.

### Used by

- **Related** [Website and regional settings](ADM-004.md): Review settings-save guidance when changes are rejected or do not appear in connected consoles.

## FAQ and troubleshooting

### Why did Save fail after another administrator changed settings?

Your console may hold an older settings revision. Reload, review the latest values and apply your changes again.

### Why can other operators see my change?

Website settings are shared and updates are sent to connected consoles.

### Can I restore yesterday's settings?

There is no general revision rollback screen. Restore the required values through the settings screens delegated to your **Settings** role. Ask Powerfront to restore values in Powerfront-managed screens.

### A save looked successful, but a value is missing. What should I do?

Reopen the screen and check the selected website. If the value is still missing, ask Powerfront support to investigate the save.