# Step 7 — Restrict platform access by IP address

> Limit access to your Personalisation Hub instance to approved IP address ranges — offices, VPN, stores and connected platforms — without locking yourself out.

How-to guide · Platform Installation › Install the platform · Last updated 15 September 2026

URL: https://personalisationhub.com/support-centre/platform-installation/step-7-restrict-platform-access-by-ip-address/

Limit access to your Personalisation Hub instance to approved IP addresses — your offices, VPN, retail locations and any connected platforms. IP restrictions are optional but recommended once installation is complete. Allow about 5 minutes, plus time to collect the address ranges.

> **Warning:** Add the IP address of the device you are using *first*. As soon as 1 address is active, every device on an address that is not listed loses access to the platform, including yours.

## Before you begin

- An HQ Admin account with the Admin role.
- The public IP address of the device you are using now (search the web for "what is my IP address").
- The IP address ranges, in CIDR notation, for every office, VPN, retail location and connected platform that needs access.

## Choose how to restrict access

**Behind your CDN.** If your organisation routes traffic through a CDN such as Akamai, place the platform behind it and add only the CDN's IP addresses in the platform. Access rules are then managed in 1 place, with the CDN's visibility of threats. Certain paths must stay publicly reachable if you use Mobile Store Sites, Virtual Queue Management or Appointment Bookings.

**Directly in the platform.** Add each approved address range in **Platform Admin → Security (IP Restrictions)**, as in the steps that follow. Up to 400 records can be defined.

## Steps

1. In the left navigation, select **Platform Admin**. The **Security (IP Restrictions)** page opens.
2. Select **Add New IP Address**.
3. Enter a **Description** that identifies the location, for example `Head office`.
4. In **Approved IP Address(es) [CIDR Schema]**, enter your current device's address in CIDR notation, for example `203.0.113.10/32`.
5. Save the entry.
6. Check that its **Activation Status** shows it as active.
7. Repeat steps 2–6 for each remaining office, VPN, retail location and connected platform range.

## Verify it worked

The record count on the page shows the number of entries you added, each with an active **Activation Status**. From a device on an address that is not listed, the platform returns an Access Denied page.

## Turn IP restrictions off

Select the select-all checkbox in the table header, then choose **Deactivate selected**. Restrictions are off whenever no IP address is defined or active; the page then shows **Currently all IP Addresses have access to the Platform.**

## Troubleshooting

### You see Access Denied straight after saving

**Cause.** The address you added is not the public address your device uses, or your network's address has changed.

**Fix.** From a device on an approved address, ask another Admin to add your current public address. If nobody can sign in, contact [support@personalisationhub.com](mailto:support@personalisationhub.com). See [I see an Access Denied error](https://personalisationhub.com/support-centre/company-set-up-and-users/i-see-an-access-denied-error/) for telling a CDN block apart from a platform block.

### Store staff or displays lose access

**Cause.** The retail location's or connected platform's address range is not listed.

**Fix.** Add the missing range with a clear **Description** and check it is active.

## Next step

Installation and set-up are complete. Continue with [Your first 30 days: the recommended set-up order](https://personalisationhub.com/support-centre/getting-started/your-first-30-days-the-recommended-set-up-order/).

## Related

- [I see an Access Denied error](https://personalisationhub.com/support-centre/company-set-up-and-users/i-see-an-access-denied-error/)
- [I can't sign in to the platform](https://personalisationhub.com/support-centre/company-set-up-and-users/i-can-t-sign-in-to-the-platform/)
- [Step 1 — Deploy the platform through AWS Marketplace](https://personalisationhub.com/support-centre/platform-installation/step-1-deploy-the-platform-through-aws-marketplace/) — why the stack's CIDR fields are left open