# Pre-installation checklist

> Every decision, account, key and asset to gather before installing Personalisation Hub, grouped by when it is needed, with the 3 permanent choices flagged.

Reference · Getting Started · Last updated 17 September 2026

URL: https://personalisationhub.com/support-centre/getting-started/pre-installation-checklist/

This checklist lists every decision and asset needed before and during installation of Personalisation Hub, grouped by when it is first needed. Items marked **Permanent** cannot be changed after installation. The step numbers refer to the articles under [Platform Installation](https://personalisationhub.com/support-centre/platform-installation/).

## AWS decisions

| Item | Needed at | Requirement |
| --- | --- | --- |
| AWS account and IAM permissions | Step 1 | An IAM user or role (not the root user) that can subscribe to AWS Marketplace products, create CloudFormation stacks that include IAM resources, request service quota increases and view billing. The full service list is in [AWS deployment: prerequisites](https://personalisationhub.com/support-centre/platform-installation/aws-deployment-prerequisites/). |
| AWS Region | Step 1 | The Region the stack is created in. **Permanent.** The platform deploys in every commercial AWS Region except GovCloud and China. |
| Service quotas | Step 1 | Review EC2, RDS, EKS, ElastiCache, OpenSearch, NAT Gateway and VPC quotas in the Service Quotas console; installation pauses if a limit is reached. |
| Stack name | Step 1 | Any name that identifies the environment in CloudFormation, with no spaces. |
| `ResourcePrefix` | Step 1 | Names every AWS resource the stack creates. **Permanent.** Maximum 15 characters, all lower-case, no spaces. |
| CIDR values | Step 1 | All 3 CIDR fields are set to `0.0.0.0/0`; IP restrictions are applied inside the platform (Step 7). |
| Environment type | Step 2 | Development, Staging or Production. |
| Environment size | Step 2 | 4 presets that set the EKS worker node size, from a proof-of-concept size through Low and Medium to High. Choose Medium or larger if you plan to use the AI features; the size can be adjusted later on the Cost Control Settings page. |
| Cost control schedule (optional) | Step 2 | Scale-down and scale-up times, and weekend scale-down, for non-production environments. See [AWS deployment: lifecycle management](https://personalisationhub.com/support-centre/platform-installation/aws-deployment-lifecycle-management/). |

## Identity, domain and keys

| Item | Needed at | Requirement |
| --- | --- | --- |
| Company / Brand Name | Step 2 | Used as the `${BrandName}` token in every SMS and email the platform sends. Match the naming your stores use in Google Maps. |
| Master Admin email | Step 2 | A shared mailbox such as `itadmin@yourdomain.com`, not 1 person's address. It is the primary platform login, receives the installation and DNS emails, and opens the Cost Control Settings page. |
| Master Admin password | Step 2 | Any password for the Installation Wizard; you must set a strong one at first login. |
| Platform domain | Step 2 | A sub-domain of your organisation's primary domain, for example `ph.yourdomain.com`. **Permanent.** It must sit on the primary domain so first-party cookies connect online and in-store journeys. |
| DNS access within 3 days | Step 3 | Someone who can add 2 CNAME records for the platform domain (behind your CDN if you use one) before the 3-day AWS certificate expires. |
| Google Maps API key | Step 2 or later | Required to add stores and look up addresses. Can be entered in the wizard or later under **Platform Admin → Google Maps/Places**. See [Connect the platform to Google Maps / Places](https://personalisationhub.com/support-centre/integrations-and-3rd-party-guides/connect-the-platform-to-google-maps-places/). |

## Platform set-up and brand

| Item | Needed at | Requirement |
| --- | --- | --- |
| Platform email address | Step 4 | A sender address on a domain you control, for example `personalisationhub@yourdomain.com`. AWS SES sends it a verification link; it must show **Verified** before you can invite users. If your AWS account is in SES sandbox mode, raise a request with AWS to move out of sandbox. |
| AWS SES Region | Step 4 | The SES Region the platform sends from, chosen in **Company Settings → Platform Set-up**. |
| HQ user list | Step 4 | Email addresses for Admin, Marketing and Helpdesk users. Invitation links expire after 24 hours; after that users use **Forgot password**. |
| Platform SMS Sender ID | Before queueing or appointments | The sender name visitors see on SMS. Defaults to `${BrandName}`; sender ID registration with AWS may be required in your country. See [Update the platform's SMS sender ID](https://personalisationhub.com/support-centre/queue-management/update-the-platform-s-sms-sender-id/). |
| Helpdesk phone number, support email address(es), privacy policy URL | Step 4 | Your organisation's own contact details and privacy policy, entered in **Platform Set-up**. |
| Primary business category | Step 5 | The category that describes your stores, for example *Mobile Phone Shop*. |
| Logos and icons | Step 5 | Company logo (transparent PNG, maximum 1 MB) and company icon (transparent PNG, maximum 512 KB), each in a version for dark backgrounds and a version for light backgrounds. SVG is not listed as a supported upload format in the current UI. |
| Brand guidelines (recommended) | Step 5, before the first campaign | A PDF the AI agents use when writing briefs and generating creative: tone of voice, colours, typography, imagery, copy rules and compliance. See [Upload your brand guidelines for the AI agents](https://personalisationhub.com/support-centre/company-set-up-and-users/upload-your-brand-guidelines-for-the-ai-agents/). |
| Target audiences and campaign objectives (optional) | Before the first campaign | Persona names and objectives the AI agents draw on. Defaults exist; see [Define target audiences and campaign objectives](https://personalisationhub.com/support-centre/company-set-up-and-users/define-target-audiences-and-campaign-objectives/). |

## Stores, staff, access and integrations

| Item | Needed at | Requirement |
| --- | --- | --- |
| Store list | Step 6 | Every store's Google Places listing, the customer-facing store name, and a unique **Store Code** per store (matching your CMS if you use AEM). |
| Retail staff CSV | Before queueing or appointments | From the template under **Company Settings → Retail Admin Set-up**: email, name, role (`Staff` or `Store_Manager`) and store code per person. Not needed if store staff will sign in through SAML. |
| SAML identity provider (optional) | Before staff onboarding | Email [support@personalisationhub.com](mailto:support@personalisationhub.com) with the subject *SAML Integration Support* to have store staff provisioned through single sign-on. See [Integrate single sign-on (SAML) for store staff](https://personalisationhub.com/support-centre/company-set-up-and-users/integrate-single-sign-on-saml-for-store-staff/). |
| IP address list | Step 7 | CIDR ranges for offices, VPN, stores and connected partner platforms — or your CDN's ranges if the platform sits behind a CDN. Add your own current address first. Maximum 400 records. |
| Display hardware | Milestone 6 | Amazon Signage Sticks or Fire TV, ChromeOS or Android players, or AEM Screens, each able to reach your platform domain. See [How displays and devices work in Personalisation Hub](https://personalisationhub.com/support-centre/digital-signage/how-displays-and-devices-work-in-personalisation-hub/). |
| AI model provider API keys (optional) | Before the first campaign created with the AI assistant | API keys from OpenAI (brief and copy) and Google Gen AI (images; Veo 3.1 for video), or LTX (LTX 2.5) for video instead of Veo, registered under **Platform Admin → AI Models / Integrations**. Not needed to write a brief yourself and upload your own creative. See [Connect AI models and providers](https://personalisationhub.com/support-centre/personalisation-and-ai/connect-ai-models-and-providers/). |
| Juniper MIST account (optional) | Before proximity personalisation | Organisation ID and API token for your MIST account, with virtual-BLE access points deployed in store. See [Enable proximity personalisation with MIST](https://personalisationhub.com/support-centre/personalisation-and-ai/enable-proximity-personalisation-with-mist/). |

> **Important:** Agree the AWS Region, the `ResourcePrefix` and the platform domain with your IT team before you start. None of the 3 can be changed once the stack is created and the platform installed.

## Related

- [Install Personalisation Hub from AWS Marketplace](https://personalisationhub.com/support-centre/platform-installation/install-personalisation-hub-from-aws-marketplace/)
- [Step 1 — Deploy the platform through AWS Marketplace](https://personalisationhub.com/support-centre/platform-installation/step-1-deploy-the-platform-through-aws-marketplace/)
- [Step 2 — Run the Installation Wizard](https://personalisationhub.com/support-centre/platform-installation/step-2-run-the-installation-wizard/)
- [AWS deployment: prerequisites](https://personalisationhub.com/support-centre/platform-installation/aws-deployment-prerequisites/)
- [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/)