Who this is for: studio operators (admin panel) · Product: Podyx V2
The Team area is where you bring other people into your studio properly, each with their own login. If you are currently sharing one password with your operators, this is the tab that fixes it.
🎥 Watch the walkthrough
🔧 Where to find it
Studio Settings → Team
ℹ️ Inviting people happens here. Building and editing the roles themselves happens in Admin Panel → Roles, near the bottom of the main menu — see Roles & Permissions.
👋 Invite your operators and staff
Use the invite form to give access to anyone who needs it. The form is the same either way, but two things happen behind it:
If they are new to Podyx, they receive an invite email and set up their own account.
If they already have a Podyx account, access is granted directly — and they now get an email telling them so, rather than being added silently and never finding out.
From the same place you can resend an invite that went unanswered, see who has accepted, and manage everyone who currently has access.
🔁 Inviting someone who already has an invitation open
If you submit an email address that already has a pending invite, the form does not quietly send a second one. It tells you which role is already pending and which role you have just asked for, and says plainly that no new invite was sent.
💡 That difference is the useful part. If the two roles do not match, you have found the real problem — someone was invited at the wrong level. Revoke the pending invite and send the right one, rather than stacking invitations.
Use the Resend or Revoke options against that person instead.
🔐 Give them the right role
Every teammate is assigned a role, and the role decides what they can see and change. Use one of the templates or build a custom role with per-tab permissions. An operator might need the calendar and sessions but nothing to do with pricing or client financials.
💡 Build the role before you send the invite. It is easier than inviting everyone first and then going back to reassign them.
💡 Start people narrower than feels necessary. It is easy and pleasant to grant more access later, and much less pleasant to explain why something got changed.
🚪 When someone leaves
Revoke their access and you are done. No password change, no telling everyone else the new one, no wondering who still has the old one written down.
Revoking now asks you to confirm first. The confirmation names the person, their email address and their role, so you can see exactly who you are about to remove before it goes through. The same confirmation appears when you revoke a pending invitation.
💡 This is worth reading rather than clicking past when two people on your team share a first name, or when you are working down a list of leavers. The email address is the part that tells you which one you have selected.
Once you confirm, the revoke happens once. A second click on the button cannot revoke the same person twice.
The change also reaches them straight away. If that teammate is logged in with Podyx open, the pages they are already looking at pick up the new permissions without waiting for a reload — so revoking access takes effect on the screen in front of them, not the next time they refresh.
⚠️ One person you cannot remove: the last remaining Owner. A studio must always have at least one, so if you are handing the studio over, add the new Owner before removing the old one.
🧠 Why it matters
Real accountability, since every action is tied to a person in the audit log.
Safer delegation. You can hand over the day-to-day without handing over everything.
Clean offboarding that takes seconds.
It scales with you, from your first hire to a full team.
✅ Summary
Build your roles in Admin Panel → Roles, then invite each person by email in Studio Settings → Team and assign them the role that matches their job. Everyone gets an email whether they are new to Podyx or already had an account. Revoking access or a pending invite asks you to confirm against the person's name, email and role first, and the change reaches any page they already have open rather than waiting for a reload. Keep permissions tight to begin with, and remember the last Owner cannot be removed.
Related: Roles & Permissions · Audit · Studio Profile & General