Refresh admin help articles for event PWA
This commit is contained in:
@@ -1,34 +1,38 @@
|
||||
---
|
||||
title: "Customer Control Center Overview"
|
||||
title: "Event Dashboard Overview"
|
||||
locale: en
|
||||
slug: tenant-dashboard-overview
|
||||
audience: admin
|
||||
summary: "Invite staff, configure branding, and understand how customer-wide settings affect every event."
|
||||
summary: "Understand event status, KPIs, and the setup checklist at a glance."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
last_reviewed_at: 2026-01-23
|
||||
owner: onboarding@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: admin-issue-resolution
|
||||
- slug: live-ops-control
|
||||
---
|
||||
|
||||
## When to read this
|
||||
Right after receiving access to a new customer account or when onboarding new staff. The Customer Control Center lives in the Admin app (Filament) and mirrors most options on desktop.
|
||||
Use this guide right after creating an event or whenever you need a quick health check before going live.
|
||||
|
||||
## Key areas
|
||||
1. **Home** – snapshot of live events, storage usage, unresolved reports.
|
||||
2. **Team** – invite admins via email, assign roles (Owner, Manager, Moderator). SSO via Azure AD/Google is available if enabled in customer settings.
|
||||
3. **Branding** – upload logos, choose accent colors, set localized welcome text shown in the guest app.
|
||||
4. **Legal pages** – edit Impressum/Privacy/AGB via the Legal resource; changes propagate instantly.
|
||||
5. **Integrations** – manage Paddle keys, RevenueCat app IDs, webhooks, and Zapier tokens. Never paste secrets into articles.
|
||||
## What the dashboard shows
|
||||
- **Event status** (Draft / Published) so you always know what guests can see.
|
||||
- **KPIs** for guests, uploads, and engagement so you can spot momentum early.
|
||||
- **Setup checklist** with the remaining steps before launch.
|
||||
- **Quick actions** that jump to tasks, Live Show, branding, and QR tools.
|
||||
|
||||
## Best practices
|
||||
- Keep at least two Owner-level accounts for redundancy.
|
||||
- Use the staging customer account to test branding or automation before touching production.
|
||||
- Document invitations in a bd issue note.
|
||||
## How to use it
|
||||
1. **Confirm the status** and keep the event in Draft until everything is ready.
|
||||
2. **Work the checklist** from top to bottom; it mirrors the most common prep path.
|
||||
3. **Check KPIs** to validate that invites and uploads are coming in.
|
||||
4. **Jump into details** (tasks, QR, Live Show) using the quick actions.
|
||||
|
||||
### Tips
|
||||
- Publish only after branding, task setup, and QR sharing are complete.
|
||||
- If uploads look low, verify that the QR or join link is visible to guests.
|
||||
|
||||
### Need more help?
|
||||
See `event-prep-checklist` for event-level prep or contact cx-team@fotospiel.app for onboarding assistance.
|
||||
See `event-prep-checklist` for the full launch steps or open `live-ops-control` during the event.
|
||||
|
||||
Reference in New Issue
Block a user