# How To Restrict Changes to Key Site Settings With BetterShield?

Stops plugins and themes changing the site address, admin email or sign-up settings.

With **[BetterShield](/)**, the site address, administrator email and who may register change only when an administrator changes them.

## What it does

**Admin-only key settings** is under **BetterShield › Protection › Hardening**. Stops plugins and themes changing the site address, admin email or sign-up settings. It is off by default.

<span id="set-it-up" aria-hidden="true"></span>

## Step 1: Open Protection › Hardening

Open **Protection › Hardening** and find **Admin-only key settings**.

<figure class="doc-shot">
  <img src="/docs/screenshots/guard-site-settings.png" alt="Restrict changes to key site settings: saved state and available controls in BetterShield." width="980" height="131" loading="lazy" decoding="async">
  <figcaption>Review the state and choices shown on your own site before applying a change.</figcaption>
</figure>

## Step 2: Restrict changes to key site settings

- Open its preview and read what will change. The preview changes nothing.
- There are no extra fields. The site address, administrator email and registration settings change only when an administrator changes them.
- Turn on the fix. If the screen asks you to confirm recovery or your password, complete that before continuing.

## Recommended settings

Our advice is to test this on staging, then apply it when the behavior fits the site. Keep a working recovery method before changes affecting sign-in or the site address.

## What it can break and how to undo

An integration changing these settings outside an administrator request may be refused. Test migration and provisioning tools first. Turn the fix off to use its undo, then check the original workflow. A change is recorded in the activity log; an undo does not erase that record.

<span id="check-it-is-working" aria-hidden="true"></span>

## Final Outcome

The row should show the fix is on. Test the affected operation with an appropriate account, then check the finding. The score and Findings update on their own after the change. If the finding stays open, press **Check Again** to see what the check still sees. A server or another plugin can enforce a setting independently, so switching BetterShield off does not necessarily remove that other protection.

<figure class="doc-shot">
  <img src="/docs/screenshots/guard-site-settings.png" alt="Restrict changes to key site settings: saved state and available controls in BetterShield." width="980" height="131" loading="lazy" decoding="async">
  <figcaption>Example Guard site settings view. Check the saved values and status on your own site.</figcaption>
</figure>

## Related

- [Hardening overview](/docs/hardening/)
- [Set up recovery](/docs/set-up-recovery/)
- [Activity log](/docs/activity-log/)

This is how you can restrict changes to key site settings with BetterShield.

Getting Stuck? Feel free to contact our [Dedicated Support Team](/support/).