On this page
Take a new organization from provisioning to a validated workspace with the alerts it needs switched on, in a week.
Who can do this: a super admin for Day 0; the organization's owner or admin for every later stop.
Before you start#
- The customer's shape is chosen: Organization types explains which blueprint fits.
- Credentials for each source are to hand (marketplace keys, ad-account tokens, a shared spreadsheet).
Steps#
Work down the table. Each step opens its own page.
| # | Do this | Who | Page | When |
|---|---|---|---|---|
| 1 | Provision the organization | super admin | Provision a new organization | Day 0 |
| 2 | Directory sign-in, white-label | super admin | LDAP/AD login, White-label | Day 0 |
| 3 | Invite members, confirm brands | owner or admin | Organization settings | Day 1 |
| 4 | Set the default page and brand | owner or admin | Default page and brand | Day 1 |
| 5 | Connect a marketplace | owner or admin | Connect a marketplace | Day 1-2 |
| 6 | Connect ad, web and search accounts | owner or admin | Connect marketing sources | Day 1-2 |
| 7 | Connect a spreadsheet | owner or admin | Connect Google Sheets | Day 1-2 |
| 8 | Load files no connector covers | owner or admin | Upload CSV or Excel files | Day 1-2 |
| 9 | Reconcile the first sync | owner or admin | Data validation | Day 2 |
| 10 | Configure AI and the assistant | owner or admin | Configure AI | Week 1 |
| 11 | Switch alerts on or off | owner or admin | Alerts and brief | Week 1 |
| 12 | Hide names before sharing a link | owner or admin | Identity masking | as needed |
| 13 | Checkpoint before a large change | owner or admin | Back up and restore | as needed |
If it fails#
A step that stalls is almost always a missing role, brand or credential. Start at Troubleshooting.