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.

AWS decisions

ItemNeeded atRequirement
AWS account and IAM permissionsStep 1An 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.
AWS RegionStep 1The Region the stack is created in. Permanent. The platform deploys in every commercial AWS Region except GovCloud and China.
Service quotasStep 1Review EC2, RDS, EKS, ElastiCache, OpenSearch, NAT Gateway and VPC quotas in the Service Quotas console; installation pauses if a limit is reached.
Stack nameStep 1Any name that identifies the environment in CloudFormation, with no spaces.
ResourcePrefixStep 1Names every AWS resource the stack creates. Permanent. Maximum 15 characters, all lower-case, no spaces.
CIDR valuesStep 1All 3 CIDR fields are set to 0.0.0.0/0; IP restrictions are applied inside the platform (Step 7).
Environment typeStep 2Development, Staging or Production.
Environment sizeStep 24 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 2Scale-down and scale-up times, and weekend scale-down, for non-production environments. See AWS deployment: lifecycle management.

Identity, domain and keys

ItemNeeded atRequirement
Company / Brand NameStep 2Used as the ${BrandName} token in every SMS and email the platform sends. Match the naming your stores use in Google Maps.
Master Admin emailStep 2A 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 passwordStep 2Any password for the Installation Wizard; you must set a strong one at first login.
Platform domainStep 2A 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 daysStep 3Someone 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 keyStep 2 or laterRequired 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.

Platform set-up and brand

ItemNeeded atRequirement
Platform email addressStep 4A 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 RegionStep 4The SES Region the platform sends from, chosen in Company Settings → Platform Set-up.
HQ user listStep 4Email addresses for Admin, Marketing and Helpdesk users. Invitation links expire after 24 hours; after that users use Forgot password.
Platform SMS Sender IDBefore queueing or appointmentsThe 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.
Helpdesk phone number, support email address(es), privacy policy URLStep 4Your organisation's own contact details and privacy policy, entered in Platform Set-up.
Primary business categoryStep 5The category that describes your stores, for example Mobile Phone Shop.
Logos and iconsStep 5Company 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 campaignA 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.
Target audiences and campaign objectives (optional)Before the first campaignPersona names and objectives the AI agents draw on. Defaults exist; see Define target audiences and campaign objectives.

Stores, staff, access and integrations

ItemNeeded atRequirement
Store listStep 6Every 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 CSVBefore queueing or appointmentsFrom 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 onboardingEmail 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.
IP address listStep 7CIDR 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 hardwareMilestone 6Amazon 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.
AI model provider API keys (optional)Before the first campaign created with the AI assistantAPI 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.
Juniper MIST account (optional)Before proximity personalisationOrganisation ID and API token for your MIST account, with virtual-BLE access points deployed in store. See Enable proximity personalisation with MIST.
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.