Frequently asked questions

No. The current service runs locally with PostgreSQL and is exposed for controlled demonstrations through Cloudflare Tunnel. AWS hosting, production backups, restore testing, monitoring and an SLA are pending purchase and acceptance.

Studio Admin is the owner’s website and brand workspace. CMS is the daily operations workspace for enquiries, students, credits, schedules, attendance, artwork and reports. They share identity and stable links, while responsibilities and permissions remain separate.

A family can unlock one student’s private area with the student name, registered mobile and a six-digit studio-issued code. It shows that student’s balance, next class, attendance and portfolio. Multi-child account aggregation is not part of v8.0.1.

No. Communication actions open the user’s Mail or Messages application with prepared text. The user reviews and sends it. Automated provider delivery, logs and retries are not claimed.

No. Staff can record purchases, refunds and credits, but payment processing and automatic accounting reconciliation are deferred.

PWE Studio provides standard templates and a migration assessment. Arbitrary files may need mapping and paid clean-up. Final import requires an exceptions report, customer approval, checkpoint, rehearsal and reconciliation.

Active recurring classes, local studio time, course details and location. It deliberately excludes student and family identities.

For v8.0.1, one campus is one tenant and subscription. A future organisation layer may aggregate isolated campus tenants without merging their operational data.

Custom domains, Stripe, Xero and provider-driven calendar/email/SMS integrations are deferred unless a signed order specifically includes implementation and acceptance.

Not yet. Role separation, password hashing and session protections exist, but privileged-account MFA is an explicit pre-production gate.