Who this is for: studio operators (admin panel) · Plan: Premium · Product: Podyx V2
Roles and permissions exist so you can stop sharing one login with your whole team. Everyone gets their own account, and you decide exactly what each person can see and change. It is the difference between trusting people and hoping nobody clicks the wrong thing.
ℹ️ Roles and permissions are a Premium plan feature. On Essential you will not see this tab. See plans and pricing.
🎥 Watch the walkthrough
🔧 Where to find it
This lives in two places, which is worth knowing before you go hunting:
Settings → Team → Roles— where you build and edit the roles themselves.Settings → Team → Members— where you invite people and assign each of them a role.
💡 Build the role first, then invite the person into it. Doing it the other way round means going back to reassign everyone.
🛠 Use a template or build your own role
Start from one of the provided role templates, or create a custom role. When you build one you give it a name and a description, and you can copy an existing role as a starting point rather than beginning from scratch.
🎛 Set permissions per tab
For each tab in the CMS you choose what the role can do:
Read
Create
Update
Delete
So an operator can see the calendar and create bookings without ever touching your pricing, and a producer can manage sessions without seeing client financials.
On a phone the permission table fits the width of the screen, so you can set a role's access without scrolling sideways.
💡 Permissions shape the interface, not just what is allowed. A role that cannot perform an action does not see its button at all — a read-only teammate browsing blocked slots or opening a studio tour sees the list and the configuration without controls they cannot use, rather than buttons that fail when clicked.
⚙️ Feature-specific permissions
Some tabs carry extra permissions in additional columns for specific Podyx features, such as resolving calendar conflicts, managing pricing rules, managing promo codes and exporting data. These are the ones worth being deliberate about, since they have the widest blast radius.
💡 The promo code permission also controls what your team can read. A redeemed promo code is shown in full only to roles that can manage promo codes — everyone else sees it masked to the first two letters, while the discount amount stays visible. Useful when affiliate and partner codes have real value.
🕒 Override Booking Rules
A role with Override Booking Rules can book outside the studio's rules from the admin panel: any free time, including outside opening hours, on closed days, and at any length up to the end of the day. It covers New session, bundle and subscription booking, Edit session, and Reschedule from the session sidebar and the Calendar. Those starts appear as compact chips in their place in the time picker, each use is written to the Audit log, and double-bookings are still refused. See Admin Bookings & Pay Later for the full detail.
Unticking Override Booking Rules on a role keeps its time pickers within your booking rules, as they always were.
⚠️ One exception: clicking a slot outside opening hours on the Calendar still books at that time, even for a role with Override Booking Rules unticked.
💡 This is a permission worth keeping with the people who genuinely take late-night or closed-day bookings. Everyone else is better off with pickers that only offer times your studio actually runs.
⏳ Extending a payment link's deadline
Extending the expiry on a session's payment link is its own permission. On the session page, the booking's payment link card carries an Extend button, and only roles with this permission see it.
Owners, studio managers and full support staff get it automatically. Custom roles do not — you grant it to them in Settings → Team → Roles.
💡 If someone on a custom role tells you the Extend button is missing, this is why. It is a permission, not a bug — grant it to their role and the button appears.
💸 Applying a price change without a payment link
When Edit session changes the price, staff can untick the payment link and apply the edit straight away, for a difference the studio collects outside Podyx. That option needs permission to send payment links, so it sits with the same roles you already trust to ask clients for money. See Sessions.
💳 Stripe checkout metadata needs billing permission
Saving the Stripe checkout metadata fields, in the Stripe Connect section of Settings → Booking → Payment, needs billing permission. Staff without it do not see the form at all. See Connect Your Payments.
📦 Extending a bundle's validity
A bundle can carry a "Use within (days)" limit, and moving one buyer's deadline later — Extend in the bundle's peek on that client's page — is a separate Bundles permission. Owners hold it and can grant it to other roles.
💡 If a teammate reports that Extend is missing from a bundle on a client's page, this is why. It is a permission rather than a fault — grant it to their role and the option appears.
Be deliberate about who gets it. This permission lets someone give away studio time that has already been paid for, so it belongs with the roles you trust to make a commercial judgement — not with everyone who can see a client record.
ℹ️ The "Use within (days)" limit itself is set on the bundle — see Bundles. Using the permission is covered in Clients.
✅ Assign and go
Once the role exists, go to Settings → Team → Members and assign it to the teammates you invited. Each person then sees only what their role allows.
The Team page accepts only the roles it offers, so a teammate always ends up on a role you can see and manage there.
ℹ️ A role can only be given to someone who is already a team member. There is no route that adds a person to your team as a side effect of assigning them a role — an invitation always comes first.
💡 If an older invitation carries a role that is no longer on offer, the panel asks you to revoke it and send a new one. Pick a current role for the new invitation.
👑 Owners are protected
Only an Owner can change an Owner's role. A studio manager or anyone else with access to the Team page cannot move an Owner to a different role.
The last remaining Owner cannot have their role changed and cannot be removed. The panel explains why rather than just refusing: a studio must always have at least one Owner.
💡 If you are handing the studio to someone else, or stepping back from it, add the new Owner first. Then the old one can be changed or removed freely.
🔑 Team changes and API keys
If your studio uses the Podyx API, the keys a teammate created go with them:
Removing someone from the team revokes their API keys. The removal dialog on the Team tab names the keys that go with the person, so you can see what will stop before you confirm. Your other owners get an email when it happens.
Moving someone off the Owner role revokes their owner keys. Their scoped keys keep working.
Saving a team member's role tells you how many API keys were revoked — every time you save, including a second save of the same person.
⚠️ Read the key names in the removal dialog before you confirm. If one of them runs your website's booking flow, that flow stops the moment the person is removed — create a replacement key from a dedicated integration account first. See The Podyx API.
The API keys panel at Settings → Booking → API keys and the Roles pages show which API key owns each default role, so you can see the link between a key and a role from either side.
ℹ️ Rescheduling sessions as staff through the API needs its own permission, sessions:staff_reschedule, which only the Owner role has by default.
⚡ Changes reach open pages
A permission change now reaches the pages a team member already has open, instead of waiting for them to reload. Take access away and it disappears from the screen they are looking at right now.
💡 This matters most when you are revoking access in a hurry — you no longer have to wonder whether someone still has the old page open.
🔔 Who hears about a permission change
When you change what a role can do, the "Your permissions were updated" notice reaches only the people who actually hold that role — and only when permissions genuinely moved.
Renaming a role, or opening one and saving it untouched, no longer announces a change to your whole team.
🧠 Why it matters
Accountability. Actions belong to a person, not to a shared password.
Fewer accidents, because people cannot change what they cannot reach.
Safer offboarding. Someone leaves, you remove one account, and their API keys go with it.
You can delegate properly rather than doing everything yourself out of caution.
✅ Summary
Build your roles in Settings → Team → Roles, from templates or from scratch, setting read, create, update and delete per tab — and pay extra attention to pricing, conflicts, promo codes and data export. Override Booking Rules lets a role book outside the studio's rules — those starts show as compact chips in the time picker — with every use in the Audit log; untick it to keep that role's pickers within your rules, bearing in mind a Calendar click outside opening hours still books. Extending a payment link's deadline is its own permission: Owners, studio managers and full support staff have it already, custom roles need it granted. Unticking the payment link to apply a price-changing edit at once needs permission to send payment links, and saving the Stripe checkout metadata needs billing permission — staff without it do not see the form. Extending a bundle's validity is a separate Bundles permission that owners can grant to other roles — keep it with the people you trust to give away paid-for studio time. Then invite each teammate in Settings → Team → Members and assign them one of the roles offered there; an older invitation with a role no longer on offer needs revoking and resending. Roles shape what people see, not just what they can do, and a change now lands on pages they already have open. Only an Owner can change an Owner's role, and your studio always keeps at least one Owner, so add a replacement before removing the current one. Removing someone revokes their API keys — the dialog names them and the other owners are emailed — moving someone off Owner revokes their owner keys while their scoped keys keep working, and saving a role always tells you how many keys were revoked. The API keys panel and the Roles pages show which API key owns each default role.
Related: Audit · Invite Your Team & Roles · Clients · Bundles · Admin Bookings & Pay Later · Sessions · Connect Your Payments · The Podyx API
