Company Set-up & Users
Platform settings, HQ Admin users, retail staff accounts, single sign-on and access control.
Company Settings and Platform Admin explained Explanation
Learn which settings live under Company Settings, which live under Platform Admin, and which article documents each page.
2Add HQ Admin, Marketing and Helpdesk users How-to guide
Invite colleagues to HQ Admin as Admin, Marketing or Helpdesk users from Company Settings → Platform Set-up, and send them their password link.
3Define target audiences and campaign objectives How-to guide
Add the target audiences (personas) and campaign objectives that every campaign brief and the AI agents draw on, under Company Settings → Campaign Settings.
4Upload your brand guidelines for the AI agents How-to guide
Give the platform's AI agents a PDF of your brand guidelines so the briefs, copy and creative they generate follow your look, feel and tone. Recommended before your first campaign.
5Upload Retail Admin users for your stores How-to guide
Create Staff and Store_Manager accounts for every store by uploading a CSV under Company Settings → Retail Admin Set-up, then share the login link.
6Integrate single sign-on (SAML) for store staff How-to guide
Let store staff and managers sign in to Retail Admin through your organisation's single sign-on by raising a SAML integration ticket with support.
7Sign in to the Retail Admin site (no SAML/SSO) How-to guide
Sign in to the staff tablet (Retail Admin) with your email address and first-time password, then set your own password.
8Add custom menu links (CTA settings) to HQ Admin and Retail Admin How-to guide
Add your own links to the HQ Admin or Retail Admin left-hand menu, show or hide the log-out button and back-link, and set the default Retail Admin profile image.
9I can't sign in to the platform FAQ
Work through the 5 most common reasons a Personalisation Hub sign-in fails, from the wrong login page to an expired invitation link.
10I see an Access Denied error FAQ
An Access Denied page means your IP address is blocked, either by the platform's IP restrictions or by your organisation's CDN. Here is how to tell which and fix it.
