Help and documentation

← Home

Fix it|Tool troubleshooting

Fix: Login, cookies, and role errors

Separate flows exist for members and staff; wrong expectations cause most login tickets.

Primary path in the app: /login

/login
Tip
Work in order from top to bottom. If nothing here matches, capture the exact error text, URL, time, and account role, then ask your studio owner or Contact with those details.

Wrong portal after login

  • Staff working the desk should use credentials issued under Team, then open /admin.
  • Members use member signup and land on /dashboard or /schedule.

Immediate logout or loop

  • Enable third-party cookies only if your host requires it; otherwise check COOKIE_SECURE and domain against your real URL (HTTPS vs HTTP).
Note
These articles describe the Fitoa product surface. Hosted behaviour also depends on your deployment environment (database, SMTP, Stripe, and signup flags). Your owner or host can confirm values in .env when a panel says something is not configured.
Important
Never paste live passwords or API keys into public AI chats. Use Settings test buttons or your host’s secure channels only.