added a help system, replaced the words "tenant" and "Pwa" with better alternatives. corrected and implemented cron jobs. prepared going live on a coolify-powered system.
This commit is contained in:
Codex Agent
37
docs/help/admin/admin-issue-resolution.de.md
Normal file
37
docs/help/admin/admin-issue-resolution.de.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "Troubleshooting & Incident-Playbooks"
|
||||
locale: de
|
||||
slug: admin-issue-resolution
|
||||
audience: admin
|
||||
summary: "Leitfäden für typische Admin-Vorfälle – von hängenden Uploads bis zu Billing-Sperren."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: reliability@fotospiel.app
|
||||
related:
|
||||
- slug: live-ops-control
|
||||
- slug: privacy-and-support
|
||||
---
|
||||
|
||||
## Upload-Vorfälle
|
||||
| Symptom | Diagnose | Lösung |
|
||||
| --- | --- | --- |
|
||||
| Warteschlange >10 Min fest | Live-Ops-Health-Widget prüfen | `php artisan media:backfill-thumbnails --tenant=XYZ` ausführen, Event neu öffnen |
|
||||
| Einzelner Gast blockiert | Geräte-Limit erreicht | Limit unter Event → Upload-Regeln erhöhen oder Gast bittet Entwürfe zu löschen |
|
||||
| Fotos ohne EXIF | Gast importiert Screenshots | Kein Fehler; Hinweis geben, dass EXIF optional ist |
|
||||
|
||||
## Zugriffsprobleme
|
||||
- **Admin kommt nicht rein**: Prüfen, ob Einladung akzeptiert wurde; über *Team → Einladung erneut senden* resetten. Bei SSO Pflicht Zuordnung kontrollieren.
|
||||
- **Gast kann nicht beitreten**: Event-Status muss *Published* sein; direkten Join-Link `https://app.fotospiel.com/join/<code>` teilen.
|
||||
|
||||
## Billing & Quoten
|
||||
- Paddle-Webhook-Fehler sperrt Uploads: `storage/logs/paddle.log` prüfen, Webhook im Paddle-Dashboard erneut senden, anschließend Abo-Status toggeln.
|
||||
- Speicher zu 90 % voll: Archivierung vorziehen oder Add-on im Paddle-Kundenportal buchen.
|
||||
|
||||
## Kommunikationsvorlagen
|
||||
Nutze die vorformulierten Antworten in `docs/content/fotospiel_howto_artikel_detailliert.md`, um Messaging konsistent zu halten.
|
||||
|
||||
### Weitere Hilfe
|
||||
Eskalation an reliability@fotospiel.app mit Event-ID, Kunde und Zeitstempel. Screenshots/Logs anhängen, wenn verfügbar.
|
||||
37
docs/help/admin/admin-issue-resolution.en.md
Normal file
37
docs/help/admin/admin-issue-resolution.en.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "Troubleshooting & Issue Resolution"
|
||||
locale: en
|
||||
slug: admin-issue-resolution
|
||||
audience: admin
|
||||
summary: "Playbooks for the most common admin-side incidents, from stuck uploads to billing locks."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: reliability@fotospiel.app
|
||||
related:
|
||||
- slug: live-ops-control
|
||||
- slug: privacy-and-support
|
||||
---
|
||||
|
||||
## Upload incidents
|
||||
| Symptom | Diagnosis | Fix |
|
||||
| --- | --- | --- |
|
||||
| Queue stuck >10 min | Check Live Ops health widget | Run `php artisan media:backfill-thumbnails --tenant=XYZ` then reopen event |
|
||||
| Specific guest blocked | Guest reached per-device limit | Increase limit under Event → Upload rules or ask them to clear drafts |
|
||||
| Photos missing EXIF | Guest imported screenshots | No action; remind them that EXIF is optional |
|
||||
|
||||
## Access issues
|
||||
- **Admin cannot log in**: verify invite accepted; reset via *Team → Resend invite*. Check SSO mapping if enforced.
|
||||
- **Guest cannot join**: confirm event status is *Published* and share direct join URL `https://app.fotospiel.com/join/<code>`.
|
||||
|
||||
## Billing & quotas
|
||||
- Paddle webhook failure locks uploads: check `storage/logs/paddle.log`, re-send webhook via Paddle dashboard, then toggle the subscription status.
|
||||
- Storage 90% full: run archive early or purchase add-on via Paddle customer portal.
|
||||
|
||||
## Communication templates
|
||||
Reuse the canned responses under `docs/content/fotospiel_howto_artikel_detailliert.md` to keep messaging consistent.
|
||||
|
||||
### Need more help?
|
||||
Escalate to reliability@fotospiel.app with the event ID, customer account, and timestamp. Attach screenshots/logs when possible.
|
||||
38
docs/help/admin/event-prep-checklist.de.md
Normal file
38
docs/help/admin/event-prep-checklist.de.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: "Checkliste Event-Vorbereitung"
|
||||
locale: de
|
||||
slug: event-prep-checklist
|
||||
audience: admin
|
||||
summary: "48-Stunden-Countdown, damit Geräte, Gäste und Automationen ready sind, bevor es losgeht."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: ops@fotospiel.app
|
||||
related:
|
||||
- slug: live-ops-control
|
||||
- slug: post-event-wrapup
|
||||
---
|
||||
|
||||
## 48–24 Stunden vorher
|
||||
- [ ] Event in der Admin-App mit korrekter Zeitzone + Aufbewahrungsfrist anlegen.
|
||||
- [ ] Titelbild (1200×630) hochladen und Übersetzungen für Titel/Beschreibung prüfen.
|
||||
- [ ] Gästelisten importieren oder QR-Badges erzeugen.
|
||||
- [ ] Push-Vorlagen testen (Reminder, Achievement-Freischaltung).
|
||||
|
||||
## 24–2 Stunden vorher
|
||||
- [ ] `tenant:attach-demo-event` im Staging ausführen, um den Ablauf mit dem Team zu proben.
|
||||
- [ ] Join-QR nahe Eingang und Fotoboxen ausdrucken oder anzeigen.
|
||||
- [ ] WLAN-SSID/Passwort-Beschilderung vorbereiten.
|
||||
- [ ] Moderationsregeln mit Kundenvertrag abgleichen (z. B. explizite Inhalte blocken, Freigabe nötig).
|
||||
- [ ] Paddle/RevenueCat-Status prüfen (alle Ampeln auf Grün).
|
||||
|
||||
## Letzte 2 Stunden
|
||||
- [ ] Demodaten aus dem Live-Event entfernen.
|
||||
- [ ] Gäste-App auf Testgeräten öffnen und den Schnellstart durchspielen.
|
||||
- [ ] Live-Ops-Ansicht auf Tablet/Laptop in Bühnennähe starten.
|
||||
- [ ] Team zu Eskalationswegen briefen (Supportkontakte, Ersatzgeräte, Foto-Guidelines).
|
||||
|
||||
### Weitere Hilfe
|
||||
Siehe `live-ops-control` für Echtzeit-Monitoring oder melde dich bei ops@fotospiel.app.
|
||||
38
docs/help/admin/event-prep-checklist.en.md
Normal file
38
docs/help/admin/event-prep-checklist.en.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: "Event Preparation Checklist"
|
||||
locale: en
|
||||
slug: event-prep-checklist
|
||||
audience: admin
|
||||
summary: "A 48-hour countdown to ensure devices, guests, and automations are ready before doors open."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: ops@fotospiel.app
|
||||
related:
|
||||
- slug: live-ops-control
|
||||
- slug: post-event-wrapup
|
||||
---
|
||||
|
||||
## 48–24 hours before
|
||||
- [ ] Create the event in the Admin app with correct timezone + retention policy.
|
||||
- [ ] Upload cover artwork (1200×630) and ensure translations exist for titles/descriptions.
|
||||
- [ ] Import guest lists or generate QR badges if needed.
|
||||
- [ ] Test push notification templates (reminders, achievement unlocks).
|
||||
|
||||
## 24–2 hours before
|
||||
- [ ] Run `tenant:attach-demo-event` in staging to rehearse workflow with staff.
|
||||
- [ ] Print or display the join QR near entrance and photobooth areas.
|
||||
- [ ] Prepare onsite Wi-Fi SSID/password signage.
|
||||
- [ ] Confirm that automatic moderation rules match the client contract (e.g., block explicit content, require approval).
|
||||
- [ ] Verify Paddle/RevenueCat status dashboards show green.
|
||||
|
||||
## Final 2 hours
|
||||
- [ ] Clear demo data from the live event.
|
||||
- [ ] Open the guest app on test devices and complete the getting-started flow.
|
||||
- [ ] Start the Live Ops screen on a tablet/laptop near the stage.
|
||||
- [ ] Brief staff on escalation paths (support contacts, backup devices, photo guidelines).
|
||||
|
||||
### Need more help?
|
||||
Open `live-ops-control` for real-time monitoring tips or reach out to ops@fotospiel.app.
|
||||
25
docs/help/admin/index.de.md
Normal file
25
docs/help/admin/index.de.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Hilfecenter für Event-Admins"
|
||||
locale: de
|
||||
slug: admin-help-index
|
||||
audience: admin
|
||||
summary: "Betriebsleitfäden für Event-Verantwortliche: Onboarding, Setup, Live-Steuerung und Nachbereitung."
|
||||
version_introduced: 2025.4
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: cx-team@fotospiel.app
|
||||
related: []
|
||||
---
|
||||
|
||||
Hier findest du alle Informationen, die du als Event-Admin für einen reibungslosen Ablauf brauchst. Die Artikel sind entlang des Event-Lebenszyklus sortiert:
|
||||
|
||||
| Phase | Leitfragen | Artikel-Slug |
|
||||
| --- | --- | --- |
|
||||
| Konto & Team | Wie lade ich Mitarbeitende ein und setze Branding auf? | `tenant-dashboard-overview` |
|
||||
| Event-Vorbereitung | Welche Checkliste erledige ich vor Einlass? | `event-prep-checklist` |
|
||||
| Live-Betrieb | Wie überwache ich Uploads, moderiere Inhalte und sende Hinweise? | `live-ops-control` |
|
||||
| Abschluss & Compliance | Wie funktionieren Export, Archiv und Datenschutz? | `post-event-wrapup` |
|
||||
| Troubleshooting | Was tun bei Upload-Problemen, Geräteverlust oder Billing-Fragen? | `admin-issue-resolution` |
|
||||
|
||||
Nutze die Navigationsleiste in der Admin-App für den Schnellzugriff oder öffne `/help/admin` im Desktop-Browser für die vollständige Ansicht mit Breadcrumbs und verwandten Artikeln.
|
||||
25
docs/help/admin/index.en.md
Normal file
25
docs/help/admin/index.en.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Customer Admin Help Center"
|
||||
locale: en
|
||||
slug: admin-help-index
|
||||
audience: admin
|
||||
summary: "Operational playbooks for event owners: onboarding, event setup, live control, and post-event delivery."
|
||||
version_introduced: 2025.4
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: cx-team@fotospiel.app
|
||||
related: []
|
||||
---
|
||||
|
||||
This portal collects everything event admins need to configure customer accounts, run events smoothly, and resolve issues quickly. Articles are grouped by lifecycle:
|
||||
|
||||
| Phase | Key Questions | Article Slug |
|
||||
| --- | --- | --- |
|
||||
| Account Setup | How do I invite staff and configure branding? | `tenant-dashboard-overview` |
|
||||
| Event Preparation | What checklists should I complete before doors open? | `event-prep-checklist` |
|
||||
| Live Operations | How do I monitor uploads, moderate content, and trigger announcements? | `live-ops-control` |
|
||||
| Wrap-up & Compliance | How are exports, archives, and privacy handled? | `post-event-wrapup` |
|
||||
| Troubleshooting | How to handle upload issues, device loss, billing, etc. | `admin-issue-resolution` |
|
||||
|
||||
Use the navigation sidebar inside the admin app for faster access, or open `/help/admin` in a desktop browser for the full layout with breadcrumbs and related links.
|
||||
39
docs/help/admin/live-ops-control.de.md
Normal file
39
docs/help/admin/live-ops-control.de.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: "Live-Ops-Steuerung"
|
||||
locale: de
|
||||
slug: live-ops-control
|
||||
audience: admin
|
||||
summary: "Uploads überwachen, Inhalte moderieren und Durchsagen versenden, während das Event läuft."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: ops@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: admin-issue-resolution
|
||||
---
|
||||
|
||||
## Dashboard-Widgets
|
||||
- **Upload-Durchsatz** – Fotos/Minute, farblich markiert bei Rückständen >25.
|
||||
- **Gerätegesundheit** – Top-Geräte mit Fehlern (Berechtigung verweigert, Speicher voll).
|
||||
- **Moderationswarteschlange** – gemeldete Fotos zur Freigabe; Moderator:innen zuweisen.
|
||||
- **Ankündigungen** – Push/Banner erstellen; Sprachversionen möglich.
|
||||
|
||||
## Typischer Ablauf
|
||||
1. Live-Ops-Seite auf Tablet anheften. Auto-Refresh auf 15 Sekunden stellen.
|
||||
2. Durchsatz beobachten, sobald Gäste eintreffen; direkt nach Zeremonien sind >40/min üblich.
|
||||
3. Wächst der Rückstau, Banner senden („Bitte kurz online bleiben“ oder „Serienaufnahme reduzieren“).
|
||||
4. Gemeldete Inhalte zügig bearbeiten; Policy verlangt Aktion innerhalb von 10 Minuten.
|
||||
5. *Achievement-Trigger* nutzen, um Badges manuell zu vergeben, falls Automationen ausfallen.
|
||||
|
||||
## Eskalationsmatrix
|
||||
| Problem | Erste Aktion | Eskalation an |
|
||||
| --- | --- | --- |
|
||||
| Upload-Warteschlange fest | Health Check ausführen → Event erneut synchronisieren | Reliability Rufbereitschaft |
|
||||
| Anstößiger Inhalt | Foto ausblenden → Beweis herunterladen → Veranstalter informieren | Legal Duty Officer |
|
||||
| Billing-Lock | Paddle-Dashboard prüfen → Zahlungsstatus bestätigen | Finance |
|
||||
|
||||
### Weitere Hilfe
|
||||
Siehe `admin-issue-resolution` für detailliertes Troubleshooting oder melde dich im Slack-Channel #ops-help.
|
||||
39
docs/help/admin/live-ops-control.en.md
Normal file
39
docs/help/admin/live-ops-control.en.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: "Live Ops Control"
|
||||
locale: en
|
||||
slug: live-ops-control
|
||||
audience: admin
|
||||
summary: "Monitor uploads, moderate content, and push announcements while the event is live."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: ops@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: admin-issue-resolution
|
||||
---
|
||||
|
||||
## Dashboard widgets
|
||||
- **Upload throughput** – photos/minute, highlighted when backlog >25.
|
||||
- **Device health** – top devices experiencing errors (permission denied, storage full).
|
||||
- **Moderation queue** – flagged photos awaiting approval; assign to moderators.
|
||||
- **Announcements** – compose push/banner messages; supports locale-specific text.
|
||||
|
||||
## Typical workflow
|
||||
1. Pin the Live Ops page on a tablet. Set auto-refresh to 15 seconds.
|
||||
2. Watch the throughput graph as doors open; expect spike to 40+/min right after ceremonies.
|
||||
3. If backlog grows, broadcast a banner reminding guests to stay online or reduce burst uploads.
|
||||
4. Moderate flagged items quickly; policies require action within 10 minutes.
|
||||
5. Use the *Achievement trigger* widget to award badges manually if automation criteria fail.
|
||||
|
||||
## Escalation matrix
|
||||
| Issue | First action | Escalate to |
|
||||
| --- | --- | --- |
|
||||
| Upload queue stuck | Run health check → re-sync event | Reliability on-call |
|
||||
| Offensive content | Hide photo → download evidence → notify organizer | Legal duty officer |
|
||||
| Billing lock | Check Paddle dashboard → confirm payment status | Finance |
|
||||
|
||||
### Need more help?
|
||||
Open `admin-issue-resolution` for detailed troubleshooting or ping #ops-help in Slack.
|
||||
33
docs/help/admin/post-event-wrapup.de.md
Normal file
33
docs/help/admin/post-event-wrapup.de.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "Nachbereitung & Abschluss"
|
||||
locale: de
|
||||
slug: post-event-wrapup
|
||||
audience: admin
|
||||
summary: "Highlights exportieren, Daten archivieren und Datenschutzpflichten binnen 72 Stunden erfüllen."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: success@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: privacy-and-support
|
||||
---
|
||||
|
||||
## Erste 24 Stunden
|
||||
- Dankes-Push/E-Mail mit kuratierten Highlights senden (bis zu 40 Fotos auswählen → *Link teilen*).
|
||||
- Admin-CSV exportieren (Uploads, Likes, Meldungen) für die eigene Ablage.
|
||||
- Moderationswarteschlange prüfen, damit keine Meldung offen bleibt.
|
||||
|
||||
## Innerhalb von 72 Stunden
|
||||
- Aktion *Archivieren & Bereinigen* starten (Einstellungen → Datenlebenszyklus). Kopiert Medien in Cold Storage und löscht temporäre Caches.
|
||||
- Gästen Download-Links bereitstellen, falls vertraglich zugesagt.
|
||||
- Bei eingegangenen DSGVO-Löschanfragen Abschluss bestätigen und Ticket-ID dokumentieren.
|
||||
|
||||
## Optionaler Follow-up
|
||||
- Event als Vorlage duplizieren für zukünftige Produktionen.
|
||||
- Erkenntnisse oder Verbesserungswünsche in `docs/todo/` festhalten.
|
||||
|
||||
### Weitere Hilfe
|
||||
Wende dich an success@fotospiel.app oder konsultiere die Legal-Pages-Ressource für Compliance-Formulierungen.
|
||||
33
docs/help/admin/post-event-wrapup.en.md
Normal file
33
docs/help/admin/post-event-wrapup.en.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "Post-Event Wrap-up"
|
||||
locale: en
|
||||
slug: post-event-wrapup
|
||||
audience: admin
|
||||
summary: "Export highlights, archive data, and fulfill privacy obligations within 72 hours after the event."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: success@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: privacy-and-support
|
||||
---
|
||||
|
||||
## First 24 hours
|
||||
- Send thank-you push/email with curated highlights (select up to 40 photos → *Share link*).
|
||||
- Export admin CSV (uploads, likes, reports) for your records.
|
||||
- Review moderation queue to ensure no reports remain unresolved.
|
||||
|
||||
## Within 72 hours
|
||||
- Trigger the *Archive & purge* action (Settings → Data Lifecycle). This copies media to cold storage and deletes transient caches.
|
||||
- Provide guests with download links if promised in the contract.
|
||||
- If GDPR deletion requests were filed, confirm completion and record the ticket ID.
|
||||
|
||||
## Optional follow-up
|
||||
- Duplicate the event as a template for future productions.
|
||||
- Update `docs/todo/` with learnings or improvements for the product team.
|
||||
|
||||
### Need more help?
|
||||
Reach success@fotospiel.app or consult the Legal Pages resource for compliance wording.
|
||||
34
docs/help/admin/tenant-dashboard-overview.de.md
Normal file
34
docs/help/admin/tenant-dashboard-overview.de.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Überblick: Kunden-Dashboard"
|
||||
locale: de
|
||||
slug: tenant-dashboard-overview
|
||||
audience: admin
|
||||
summary: "Mitarbeitende einladen, Branding konfigurieren und globale Kundeneinstellungen verstehen."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: onboarding@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: admin-issue-resolution
|
||||
---
|
||||
|
||||
## Wann lesen?
|
||||
Direkt nach dem Zugriff auf einen neuen Kunden oder wenn neue Mitarbeitende eingearbeitet werden. Das Kunden-Dashboard befindet sich in der Admin-App (Filament) und bietet auf Desktop dieselben Optionen.
|
||||
|
||||
## Hauptbereiche
|
||||
1. **Home** – Überblick über laufende Events, Speicherauslastung und offene Meldungen.
|
||||
2. **Team** – Admins per E-Mail einladen, Rollen vergeben (Owner, Manager, Moderator). SSO via Azure AD/Google möglich, falls im Kundenkonto aktiviert.
|
||||
3. **Branding** – Logos hochladen, Akzentfarben wählen, lokalisierten Begrüßungstext für die Gäste-App setzen.
|
||||
4. **Rechtliches** – Impressum/Datenschutz/AGB über die Legal-Ressource pflegen; Änderungen greifen sofort.
|
||||
5. **Integrationen** – Paddle-Keys, RevenueCat-App-IDs, Webhooks und Zapier-Tokens verwalten. Keine Secrets in Dokumente kopieren.
|
||||
|
||||
## Best Practices
|
||||
- Mindestens zwei Owner-Rollen für Redundanz halten.
|
||||
- Branding oder Automationen zuerst im Staging-Kundenkonto testen.
|
||||
- Einladungen im Änderungslog (`docs/changes/`) dokumentieren.
|
||||
|
||||
### Weitere Hilfe
|
||||
Siehe `event-prep-checklist` für Event-Vorbereitung oder kontaktiere cx-team@fotospiel.app für Onboarding-Support.
|
||||
34
docs/help/admin/tenant-dashboard-overview.en.md
Normal file
34
docs/help/admin/tenant-dashboard-overview.en.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Customer Control Center Overview"
|
||||
locale: en
|
||||
slug: tenant-dashboard-overview
|
||||
audience: admin
|
||||
summary: "Invite staff, configure branding, and understand how customer-wide settings affect every event."
|
||||
version_introduced: 2025.4
|
||||
requires_app_version: "^3.2.0"
|
||||
status: draft
|
||||
translation_state: aligned
|
||||
last_reviewed_at: 2025-02-22
|
||||
owner: onboarding@fotospiel.app
|
||||
related:
|
||||
- slug: event-prep-checklist
|
||||
- slug: admin-issue-resolution
|
||||
---
|
||||
|
||||
## 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.
|
||||
|
||||
## 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.
|
||||
|
||||
## 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 the change log (`docs/changes/`).
|
||||
|
||||
### Need more help?
|
||||
See `event-prep-checklist` for event-level prep or contact cx-team@fotospiel.app for onboarding assistance.
|
||||
Reference in New Issue
Block a user