Event Setup Guide (v3 Admin)

This guide is for setup managers and event admins who configure events in the TogoActive v3 Admin. It walks through every menu in the admin, explains what each setting does, and — most importantly — tells you exactly which part of the public white-label (WL) event site each setting affects. No coding knowledge is required; developer details live in the companion docs.

Related docs: Architecture Overview · Admin Frontend · WL Frontend

---

1. How the platform fits together

The v3 platform has three moving parts that share one database. The Admin (the React app you log into) is where you configure everything: event details, pages, images, emails, features, payments. Every save in the admin writes to the shared database. The WL API reads that database and serves it to the public WL site — the event website participants actually see (landing page, registration, leaderboards, profiles, donations). In short: you edit in the admin → the database changes → the public site renders the new state. There is no separate "publish" step for most settings; saving is publishing.

Two things can make a change look like it "didn't work" when it actually saved fine. First, caching: the public site caches event data for about 60 seconds. When you save content or feature changes, the admin pings the WL cache to revalidate, but if you're checking immediately, do a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) on the public page — or simply wait a minute. Second, preview iframes: the live previews inside the admin (Appearance, Form Builder, Page Builder) talk to the real WL site, so what you see in the preview is genuinely what participants will see — including unsaved draft changes in the Form Builder preview.

One infrastructure caveat worth knowing: the platform runs on two servers. The admin and staging site live on one; the production WL API (wl-api.togoparts.com) lives on another. A few admin features — notably email template preview and Send Test, and the donation picker — call the production WL API directly. If that server is running an older deployment, email previews can break in the admin even though everything else works. If email preview fails, tell your developer to redeploy the production WL API — your templates and data are fine.

---

2. Setting up a new event, step by step

When you create a new event, the platform automatically seeds a default menu, default pages, and feature defaults based on the event mode you choose. Your job is to fill in the specifics. Work through this list in order — later steps depend on earlier ones.

Phase A — Foundations

1. Create the event from the main Events page. Choose the correct mode up front (Standard / Seasonal / Donation) — the mode sets sensible defaults for ~130 feature flags (see Section 4). You can change flags later, but starting with the right mode saves a lot of toggling.
2. Setup → General Info — set the event name, slug (URL), tagline, and description. The slug becomes part of the public URL, so get it right before sharing links.
3. Setup → Dates & Schedule — fill in all 8 date fields (registration start/end, event start/end, leaderboard start/end, etc.). Saving is blocked until the dates validate. These dates control when registration opens and closes on the public site, so treat them as authoritative.
4. Setup → Feature Settings — review the mode defaults and switch on/off what this event needs (teams, merchandise, donations, achievements, etc.). Note: turning features off also hides the related admin menu items, so if you can't find a menu later, come back here.

Phase B — Look and feel

5. Setup → Branding & Images — upload the cover image, icon, favicon, event name image, and other slots. Critical gotcha: uploading and cropping an image does not save it. You must also click the page's Save so the image URL is written to the event. Upload → crop → Save, every time.
6. Setup → Appearance — set brand colors, fonts, corner radii, header layout, and the hero call-to-action. The live preview shows the real public site, so you can iterate safely before saving.
7. Setup → Event Host — fill in the host/organizer profile (name, logo, description). This powers the host card on the public site and the host avatar shown around the event.
8. Setup → Social & SEO — add social media links (blank links are hidden on the site; if you set none at all, togoparts defaults appear) and the share image used when links are posted to social media.
9. Setup → SEO Templates — set per-page-type meta titles/descriptions with {{tokens}} for landing, participants, leaderboard, and other pages.

Phase C — Registration and commerce

10. Registration → Registration Settings — configure the gates: referral codes, coupons, delivery address collection, free registration, and the two special toggles (re-registration for QA testing, early registration for soft launches).
11. Registration → Form Builder — build the registration form fields and intro content. Use the other tabs as needed: Merchandise copy, Qualification, Success Page, Account Details, and Upgrade (post-registration "Buy Merch"). The live preview pane shows the real registration page as participants will see it.
12. Rewards → All SKUs — create the merchandise/reward SKUs, set sizes/customizations, drag to set display order. Add Instructions (shown at the top of the merch step), Discounts (multi-quantity), and Coupon Manager codes if applicable.
13. Donations → Donation Config and Fundraiser Goals — for fundraising events, configure the donation form, recipient types, anonymous/tax options, and the goal presets participants can pick from.
14. Payments → Payment Gateway — replace the default test credential. New events fall back to a shared TEST Stripe credential (togopart-test). Real money will not flow until you select the event's real Stripe credentials here. This is the single most commonly missed launch step.

Phase D — Content and site structure

15. Content → Pages — review the seeded pages (landing = slug home) and build any custom pages with the drag-and-drop Page Builder.
16. Content → Menu Setup — choose which pages appear in the public site's header navigation, with optional conditions (logged-in only, user type, event period).
17. Content → FAQ Manager / Landing Page FAQ / Rules Manager — fill in the full FAQ page, the short home-page FAQ, and the event rules.
18. Setup → Default Messages — set default bios, share text, success-page copy, and donation copy. These feed profile bios and share texts across the site.
19. Setup → Email Branding and Email Templates — set email header/footer logos and colors, then review each template with the live preview and Send Test.

Phase E — Teams, leaderboard, extras (as needed)

20. Teams → Team Settings — enable and configure teams if the event uses them.
21. Leaderboard → General Settings / Event Highlights / Sync Settings — configure public leaderboard behavior, highlight slides, and activity sync.
22. Achievements → Achievement Groups / Achievement List — set up badges with images and earning conditions.
23. Setup → Integrations — connect GA4, GTM, Meta Pixel, or Contentsquare so marketing gets analytics from day one.
24. Setup → Avatars — curate the avatar sets participants without photos will be auto-assigned from.
25. Setup → Members & Access — add teammates who need admin access, with the right role (viewers are read-only).
26. Setup → Custom Domain (if the event gets its own domain) — add the domain, complete TXT/DNS verification, then sync. Allow time for DNS + SSL.

Launch checklist

Before announcing the event, verify all of these:

#	Check	Where
1	Real Stripe credentials selected (not togopart-test)	Payments → Payment Gateway
2	All 8 dates correct; registration opens when expected	Setup → Dates & Schedule
3	Do a full test registration end-to-end (form → merch → payment → success page → confirmation email)	Public site
4	Test a donation, if the event takes donations	Public site
5	Images visible on the live site (uploaded and saved)	Setup → Branding & Images
6	Custom domain verified, synced, and loading over HTTPS	Setup → Custom Domain
7	Emails render correctly — use Send Test on key templates	Setup → Email Templates
8	Header navigation shows the right pages	Content → Menu Setup
9	Feature Settings match the event plan (no missing/extra features)	Setup → Feature Settings
10	Early-registration / re-registration toggles set correctly for launch (usually off)	Registration → Registration Settings
11	Analytics tags firing (GA4/GTM/Pixel)	Setup → Integrations
12	Team members have correct access roles	Setup → Members & Access

Tip: use Registration Settings → allow re-registration during testing so your test account can register repeatedly (it bypasses the gates). Turn it off before launch.

---

3. Menu-by-menu reference

Main sidebar (global, not per-event)

Menu	What it does
Dashboard	Cross-event overview.
Events	List of all events; create new events here.
Users	Admin users and their platform roles (not participants).
Participants	Cross-event participant search.
Activities	Cross-event activity view.
Settings	Platform-level settings.
Global avatar library (/avatars/global)	Shared avatar sets (male_classic / female_classic / animal) available to all events.

Everything below lives in the per-event sidebar (open an event first). Remember: some items hide when their feature flag is off — Form Builder, the whole Teams group, Discounts, Coupon Manager, Event Highlights, Sync Settings, the Achievements group, Activity Manager, and Port Users are all flag-gated.

---

Event Dashboard

The event's home screen: headline numbers and quick status. Read-only; nothing here changes the public site.

Analytics

The event analytics dashboard — registrations, donations, and activity data (activity/Strava data comes from the Togoparts database). Tabs are fault-tolerant: if one data source is unavailable, the other tabs still load. Read-only.

---

Setup group

General Info

• Configures: event name, slug, tagline, description, and mode (Standard / Seasonal / Donation).
• Affects on WL: the header title, SEO fallbacks when no template is set, and the event lifecycle. The mode drives the default state of ~130 feature flags in 8 groups (see Section 4).
• Gotcha: changing the slug changes public URLs. Set the mode correctly at creation time; changing it later re-baselines feature defaults.

Dates & Schedule

• Configures: 8 date fields — registration start/end, event start/end, leaderboard start/end, and related dates. All are validated together; Save stays disabled until the dates are consistent.
• Affects on WL: registration gating (visitors see not started / open / ended messaging as appropriate), countdowns, the header button (JOIN NOW vs EVENT ENDED), when the leaderboard starts, and the fundraising deadline (which is computed on the server from the event end date).
• Gotcha: almost every "why can't people register?" question traces back to this page. Check it first.

Branding & Images

• Configures: the event's image slots — cover, icon, favicon, event name image, and more. Uploads go to the CDN (DigitalOcean Spaces) with a mandatory crop step; you can free-crop or lock the aspect ratio.
• Affects on WL: header logo, browser favicon, landing hero, and social share cards.
• Gotcha (important): uploading does not save. The upload puts the file on the CDN, but the event only uses it after you click the page's Save. If an image "disappears" after you leave the page, this is why — re-upload and save.

Appearance

• Configures: design tokens — colors, fonts, corner radii, header layout, hero call-to-action.
• Affects on WL: the entire site theme (CSS variables) and Google-font loading.
• Gotcha: the preview iframe is the real public site, so trust what you see. Remember the public site's 60-second cache when checking outside the preview.

Event Host

• Configures: host/organizer profile and host-level donation configuration.
• Affects on WL: the event host card block on pages, and the host avatar. The avatar resolves in a cascade: host logo → organizer profile image → the host's Togoparts profile photo → a default. Upload a host logo here to control it directly.

Social & SEO

• Configures: social media links and the social share image.
• Affects on WL: footer social icons and link-share cards.
• Gotchas: a blank link hides that icon; per-link toggles let you hide filled-in links too; if you set no socials at all, togoparts defaults appear — so set at least one if you don't want defaults.

SEO Templates

• Configures: meta title/description templates per page type (landing, participants, leaderboard, …) using {{tokens}} that fill in event data.
• Affects on WL: the <head> metadata search engines and social platforms read.
• Gotcha: the separate Per-Page Meta editor inside Form Builder pages applies only to the registration and upgrade pages. For landing/participants/leaderboard, use SEO Templates — not Per-Page Meta.

Custom Domain

• Configures: attaching the event's own domain (e.g. myevent.com).
• How it works: add the domain → complete TXT record + DNS verification → Sync. Syncing provisions the web-server configuration and SSL certificate on the WL server. The public site then recognizes the domain automatically, and all generated links (including Stripe payment redirects) become custom-domain aware.
• Gotcha: DNS changes take time to propagate. Verify well before launch day, and re-check HTTPS works.

Email Branding

• Configures: email header/footer logos and colors used across all event emails.
• Defaults: empty header, togoparts footer, sender no-reply@togoparts.com.

Email Templates

• Configures: the content of each transactional email (registration confirmation, donation receipt, etc.) in a template designer with live preview and Send Test.
• Gotcha (important): preview and test-send go through the production WL API server. If that server has a stale deployment, previews break in the admin only — real emails and your saved templates are unaffected. Ask a developer to redeploy the production WL API.

Default Messages

• Configures: default participant bios, share text, success-page copy, and donation copy (stored as the event's default-message configuration).
• Affects on WL: profile bios, share texts (via {{share_text}}-style tokens), and success pages.
• Note: an individual participant's profile-share text uses their pledge message (fundraising description), shown at full length.

Feature Settings

• Configures: every feature flag for the event — ~130 flags in 8 groups. The event mode sets the defaults; you can override any flag; the page tracks how many flags you've overridden and offers Reset All back to mode defaults. A banner shows the current mode.
• Affects on WL: features gate the public flow (e.g. the merchandise flag gates the merch step in registration; the Upgrade tab's step-count enable gates the post-registration "Buy Merch" page).
• Affects in admin: flag-gated sidebar items appear/disappear. The sidebar sections themselves stay visible, but disabled sections show a banner.

Integrations

• Configures: analytics/marketing tags per event — GA4 (OAuth connect and pick a property), GTM, Meta Pixel, Contentsquare.
• Affects on WL: the tags are injected into every public page. Registration funnel events fire automatically (registration_started, step progress, registration_submitted, upgrade_started).

Avatars

• Configures: the event's curated avatar sets (male / female / gender-neutral), drawing on the global library.
• Affects on WL: participants who register without a photo are auto-assigned a gender-matched avatar; participants can also pick a curated avatar from their profile page.

Members & Access

• Configures: the per-event admin team. Roles: owner / admin / editor / viewer.
• Gotcha: viewer is genuinely read-only — the server rejects their write attempts. If a teammate reports that saving fails everywhere, check their role here.

---

Registration group

Registration Settings

Toggles that gate the public registration flow:

Toggle	Effect
Referral	Collect referral codes at registration
Coupon	Allow coupon codes
Delivery address	Collect a shipping address
Free registration	No payment required
Allow re-registration	QA tool — lets the same account register again, bypassing gates. Turn off for launch.
Allow early registration	Soft launch — permits registration before the official start (never after end)

Form Builder

• Configures: the registration experience across tabs — Registration Form (fields + intro content blocks), Merchandise (step copy), Qualification, Success Page, Account Details, and Upgrade (the post-registration "Buy Merch" flow; its step-count enable switch turns the /upgrade page on/off).
• How it looks: a 3-panel editor — field/section tree on the left, a live preview of the real WL registration page in the middle (it shows your unsaved changes), and a settings drawer on the right.
• Affects on WL: registration is a 3–5 step flow: Registration → (Merchandise) → (Qualification/Donation) → Summary, with Stripe checkout for paid carts and donations.
• Good to know: step 1 partially registers the participant immediately — people who abandon mid-flow still appear in your participant counts, which is intentional (you can follow up with them).

---

Teams group (hidden when teams are disabled in Feature Settings)

Team Settings

Enable and configure teams for the event (team creation rules, sizes, etc.). Affects whether the public site offers team join/create during and after registration.

All Teams

Roster management: view teams, move members between teams, set the team owner, rename, and delete.

• Gotchas: renaming a team also syncs the name shown on the Togoparts leaderboard (handled automatically — just be aware the name changes everywhere). Deleting a team whose members purchased SKUs is blocked with a friendly error rather than allowed.

---

Rewards group

All SKUs

Create and manage merchandise/reward SKUs: pricing, sizes, customizations, visibility, and drag-to-reorder (the order here is the display order on the public site). You can import SKUs from other events to save setup time.

Instructions

Rich-text copy shown as the intro at the top of the merchandise step on the public site. This is the highest-priority intro copy for that step — if you set it, it wins.

Discounts (flag-gated)

Multi-quantity discounts (e.g. buy 2, save X).

Coupon Manager (flag-gated)

Coupon codes, plus the returning-participant default coupon — a coupon auto-applied on the public site for participants who joined a previous event.

---

Donations group

Donation Config

• Configures: donation form behavior, recipient types (event / participant / team), anonymous-donation and tax-deduction options.
• Affects on WL: the donate pages and, when tax options are on, the capture of tax-deduction details from donors (works for all recipient types, including team donations).

Fundraiser Goals

• Configures: the goal presets participants pick from, and the Update Goals modal behavior.
• Gotchas: removed preset chips stay removed after save (this used to be buggy; it now persists correctly). The fundraising deadline is derived from the event end date — set it in Dates & Schedule, not here.

---

Content group

Pages

The full drag-and-drop Page Builder with roughly 80 block types: hero, headings, text, images, carousels, leaderboard, participants, FAQ, fundraiser, donation, and profile blocks, plus an AI assistant panel, page templates, and import/export.

• Every page has a slug; the landing page is the page with slug home.
• System page types (user detail, team detail, donation, my profile, …) power the dynamic URLs like /user/{id} and /team/{id} — don't delete these.
• What you build is rendered 1:1 on the public site by the same block renderer, so the editor preview is faithful.

Menu Setup

Choose which pages appear in the public site's header navigation, in what order, with optional conditions: show only to logged-in users, only to certain user types, or only during a certain event period.

FAQ Manager

The full FAQ page (slug faq), built from FAQ blocks with production-parity header and footer.

Landing Page FAQ

A separate, short FAQ shown on the home page. Editing one does not change the other — a common mix-up.

Rules Manager

The event rules content page.

---

Leaderboard group

General Settings

Public leaderboard toggles — what leaderboards are shown and how.

Event Highlights (flag-gated)

A carousel of rich, block-based slides edited in a full-screen block editor, with a ShortCodes dropdown for inserting {{token}} placeholders that fill in live event data.

Sync Settings (flag-gated)

Gallery and activity sync configuration.

---

Achievements group (flag-gated)

Achievement Groups / Achievement List

Define achievement groups and individual achievements: badge image, more-info image, sponsor image, and the conditions for earning them.

• Affects on WL: the achievements gallery page and the Trophy tab on participant profiles.
• Good to know: winners are assigned by scheduled jobs (crons), so badges appear on a schedule rather than instantly. (Technically: the legacy system's cron does the winner assignment for all events; only the unlock email differs — sent by the legacy system for events below 49 and by v3 for 49 and above. A developer detail, but useful if badge assignment seems delayed.)

---

Communications group

Notifications

Placeholder — not yet functional.

Automation Rules

Per-event email automations (trigger-based sends) with a test-send option.

Email Logs

A delivery audit of every email sent for the event, with per-email preview. Your first stop for "the participant says they never got the email."

---

Payments group

Payment Gateway

Pick which Stripe credentials (from the shared credential library) the event charges through.

• Gotcha (critical): new events default to the shared TEST credential togopart-test. Test payments succeed against it, which makes it easy to miss. Replace it with the real credential before launch. It's #1 on the launch checklist for a reason.

Transaction History

All payments for the event with stats, filters, and export. Read-only.

---

Operations group

Participants

The event's participant operations console: search/filter/export, edit registration answers, add remarks, toggle featured status, edit reward sizes and delivery addresses, issue e-bibs and e-certs, trigger a Strava re-sync, view payment and audit history, and remove participants.

Activity Manager (flag-gated)

Review, exclude, and audit submitted activities; batch operations; a suspicion panel for flagging dubious entries.

Re-sync Activities

Placeholder — not yet functional.

Port Users (flag-gated)

A 5-step wizard to migrate participants from one event to another, with dry-run mode, conflict handling, and a history view with revert. Always dry-run first (see recipe in Section 5).

---

Developer Tools group

Configuration Store, Custom CSS/JS, and OneSignal Setup are placeholders. Ignore them for event setup.

---

4. Event modes & feature settings explained

Every event has a mode, chosen on General Info:

Mode	Internal name	Typical use
Standard	default_mode	Classic activity challenge with leaderboards
Seasonal	sessionalmode	Season-long / recurring-session events
Donation	donation_mode	Fundraising-first events

The mode does one job: it sets the default value of every feature flag — roughly 130 flags organized into 8 groups on the Setup → Feature Settings page. A donation-mode event starts with donation features on and merch-heavy features off; a standard event starts the other way around.

Key things to understand:

1. Mode sets defaults, you set reality. Any flag can be overridden regardless of mode. The page shows a banner naming the current mode and tracks how many flags you've overridden; Reset All returns everything to mode defaults.
2. Flags gate the public site. Examples: the registration merchandise flag controls whether the merch step exists in registration; the Upgrade tab's enable switch controls whether the /upgrade "Buy Merch" page exists at all.
3. Flags gate the admin too. Disabled features hide their menu items (Form Builder, Teams, Discounts, Coupon Manager, Event Highlights, Sync Settings, Achievements, Activity Manager, Port Users). Sidebar sections remain visible, with a banner on disabled ones. "I can't find menu X" almost always means its flag is off.
4. Changes propagate like any other save — allow up to 60 seconds (or hard-refresh) for the public site to reflect a flag flip.

---

5. Common tasks

Launch a donation event

1. Create the event with mode Donation.
2. Setup → Dates & Schedule — set all dates (the fundraising deadline follows the event end).
3. Donations → Donation Config — set recipient types, anonymous and tax-deduction options.
4. Donations → Fundraiser Goals — define the goal presets participants choose from.
5. Setup → Default Messages — write the donation copy and share text.
6. Payments → Payment Gateway — select the real Stripe credential.
7. Test: register, set a goal, make a small test donation, and confirm the receipt email and (if enabled) tax-details capture.

Enable merchandise + the post-registration "Buy Merch" (upgrade) flow

1. Setup → Feature Settings — enable the registration merchandise flag.
2. Rewards → All SKUs — create SKUs with sizes/prices; drag into display order.
3. Rewards → Instructions — write the merch-step intro copy.
4. Registration → Form Builder → Merchandise tab — set the step copy.
5. Registration → Form Builder → Upgrade tab — configure it and switch the step enable on; this activates the /upgrade page and the header Buy Merch button for registered participants.
6. Optionally add Discounts and Coupon Manager codes.
7. Test both paths: buying during registration, and buying later via Buy Merch.

Set up teams

1. Setup → Feature Settings — enable teams (the Teams menu group appears).
2. Teams → Team Settings — configure creation rules and sizes.
3. After launch, manage rosters in Teams → All Teams (move members, set owners, rename — renames flow through to the leaderboard automatically).

Add a custom page to the site menu

1. Content → Pages — create the page in the Page Builder, give it a clear slug, and save.
2. Content → Menu Setup — add the page to the header navigation; set conditions if it should only show to logged-in users or during a certain period.
3. Hard-refresh the public site (or wait ~60s) and confirm the nav item and page.

Connect Google Analytics (GA4)

1. Setup → Integrations — click connect on GA4 and complete the Google OAuth flow.
2. Select the GA4 property for this event and save.
3. Visit the public site and confirm hits in GA4 Realtime. Registration funnel events (started / step / submitted / upgrade started) fire automatically.

Port participants from an old event

1. Operations → Port Users — start the 5-step wizard, choosing source event and participants.
2. Run the dry run first and review the conflict report.
3. Resolve conflicts, then execute the real port.
4. Verify in Operations → Participants; if something is wrong, use the history + revert option.

---

6. Troubleshooting

Symptom	Likely cause	Fix
I saved a change but the public site still shows the old version	The ~60-second WL cache, or your browser cache	Wait a minute, then hard refresh (Ctrl+Shift+R). If the admin itself looks stale after a code update, a developer needs to rebuild the admin's static bundle — the admin is served from a pre-built dist/, not live code.
Email template preview or Send Test fails / looks broken	The production WL API (wl-api.togoparts.com) has a stale deployment — preview goes through it	Your templates are safe. Ask a developer to redeploy the production WL API. Everything else in the admin is unaffected.
I uploaded an image but it's gone / not on the site	Upload alone doesn't save — the slot URL was never written	Go back to Setup → Branding & Images, upload + crop again, and click Save before leaving the page.
Public site shows an "event not connected" page (intermittently)	Server-side hiccup (historically a dev-server/rate-limit issue, mitigated by frontend caching)	Refresh; if it persists, escalate to a developer — it's an infrastructure issue, not an event configuration problem.
A teammate can see everything but every save fails	They have the viewer role — read-only is enforced by the server	Setup → Members & Access — raise their role to editor/admin.
A menu item is missing from the event sidebar (Form Builder, Teams, Coupon Manager, Achievements, Port Users, …)	Its feature flag is off — flags hide their menus	Setup → Feature Settings — enable the feature. Also check the mode: a Donation-mode event ships with different defaults than Standard.
Participants can't register	Dates, gates, or payment	Check Dates & Schedule first (is registration open?), then Registration Settings (early-registration off before start?), then Payment Gateway (a broken credential blocks paid registration — though a brand-new event will "work" on the shared test credential, which is worse: check you're not still on togopart-test).
My test account can't register a second time	Re-registration gate (working as designed)	Temporarily enable allow re-registration in Registration Settings; turn it off before launch.
Registration numbers include people who never finished	By design — step 1 partially registers immediately so abandoners are counted	Use the Participants page filters to distinguish completed vs partial registrations.
Badges/achievements aren't appearing right away	Assigned by scheduled jobs, not instantly	Wait for the next cron run; if nothing after several hours, escalate.
Landing/leaderboard page titles wrong in Google/social previews	Editing Per-Page Meta instead of SEO Templates	Per-Page Meta only covers registration + upgrade. Use Setup → SEO Templates for everything else.
Footer shows togoparts social icons I didn't add	No social links set at all → defaults kick in	Add at least one link in Setup → Social & SEO, or accept the defaults.

Golden rules, if you remember nothing else:

1. Upload ≠ Save. Always hit Save after uploading images.
2. Replace togopart-test before launch.
3. Hard-refresh before assuming a save failed — the public site caches for ~60 seconds.
4. Missing menu? Check Feature Settings.
5. Broken email preview ≠ broken emails — it's the production WL API deployment.