WYA administrator guides (staging)

These guides describe the new WYA administrator workspace on staging: beti.worldyogaalliance.org. Open the workspace at /admin after signing in with an administrator account. The English labels in these guides are the labels currently rendered by the application, so you can search for the same words on the screen.

The staging workspace is a separate application from the member area. A member account cannot sign in to it. Staging is available for authorized staff review and sends a crawler-exclusion header; that marker does not restrict access. Do not put passwords, tokens, private payment details, or personal data in support tickets or documentation.

Choose a task

• Sign in, understand roles, and manage access
• Read the overview and work queues
• Manage schools, teachers, users, reviews, and media
• Create and maintain WYA events
• Review bookings, cancellations, and community-event invitations
• Maintain content, SEO, translations, videos, and courses
• Manage certificate templates and issue certificates
• Manage orders, invoices, payments, and reconciliation
• Manage affiliate commissions and organizer payouts
• Maintain system records, notifications, audit history, and reference data
• Read the separate legacy Django admin inventory

Before you change a record

1. Confirm that you are on the staging hostname and that the page header says Admin workspace.
2. Check the current record, status, owner, and public link before editing.
3. Make one focused change, select the screen’s save action, and wait for the success or error message.
4. Reopen the record or public preview to confirm the result. A success message is not proof that a page is visible; publication and visibility are separate controls in several workspaces.
5. Record the reason for an operational or financial decision in the field provided. Audit history records administrator actions.

Staging and legacy boundaries

The new workspace is the source for these guides. The production site remains the legacy acceptance baseline while migration work continues. The sidebar still exposes a Legacy module map containing read-only records from the older Django-backed modules. Those links are an inventory of legacy records; they do not mean that the old Django admin, its member authentication, or every legacy workflow has been recreated in the new workspace.

The guides explain what the source currently renders. Labels, validation rules, available reference values, and hosted data can change. When a staging screen differs, capture the exact label and route, then update the guide after the source behavior is reconciled.