Skip to main content

Studio collaboration: sharing events into a hosting studio's schedule and what clients see

How a partner studio shares classes, courses, and workshops into a hosting studio's schedule, what clients see, and how pricing and bookings work.

This article is about studio collaboration: how a partner studio shares its classes, courses, and workshops into a hosting studio's schedule, what clients see in the calendar, and how pricing, payments, and bookings work for these shared collaboration events. It isn't about the Share event button, which only copies or posts a link to one of your own events — for that, read Share Your Event.

How to share events with a hosting studio

Event sharing is always configured by the partner studio — the studio that created and owns the events. You can share any class, course, or workshop with one or more hosting studios.

When creating a new event

If you have an active collaboration, the event creation form for classes, courses, and workshops will include a Share with collaborating studios section.

  1. Create the event as usual (fill in the name, time, capacity, etc.).

  2. In the Share with collaborating studios section, check the studios you want to share the event with.

  3. Save the event.

The selected studios will see the event in their calendar, and their clients will be able to book a spot.

For an existing event

You can also turn sharing on or off for events that already exist.

  1. Open the event detail (class, course, or workshop).

  2. In the Share with collaborating studios section, toggle the switch for the relevant studio.

The change takes effect immediately — turning the toggle on adds the event to the hosting studio's calendar; turning it off removes it.

What clients of the hosting studio see

Shared events appear to the hosting studio's clients in several places.

In the calendar and schedule

Shared events are displayed directly in the hosting studio's calendar alongside its own classes. They are visually distinct from the studio's own events:

  • Classes — the calendar card shows a small link icon (chain) before the name.

  • Courses and workshops — the list cards show a purple Collaborations badge. They don't have the link icon in the calendar.

  • Event detail — the open detail (drawer) for shared classes shows a purple Collaborations badge, and above the pricing options and payment methods there is a prominent notice that this is a partner's event with its own pricing and payment terms.

In the event detail (admin view)

When the hosting studio admin opens the detail of a shared event, they will see:

  • A red notice: "Booking management, event details, and pricing are handled by [partner name]. To make changes, go to that studio's admin."

  • The cancel button is always disabled, with the tooltip "This event is managed by the partner studio. Only the studio that created it can cancel or edit it." Pricing and payment methods can only be changed by the partner studio.

  • Other actions depend on the permissions the partner studio has granted: View attendees, Manage bookings (book spots for the hosting studio's clients), Bulk message to attendees, Edit events (edit details, add course sessions, and manage courses), and Share statistics. Without a permission, the matching action isn't shown.

  • Use as a template is greyed out for shared courses and workshops, with the tooltip "Events from collaborating studios can't be used as a template."

Public links

Public links for shared events (e.g. a link to a course detail in the public widget on the studio's website) point to the partner studio's website and open in a new browser tab. The client is taken to the partner's environment, where they complete the booking and payment.

How pricing and payments work

Pricing and payment methods for shared collaboration events are always set by the partner studio. The hosting studio cannot change them.

In the event detail, a notice is displayed above the prices: "Pricing and payment terms are set by [partner name]."

This means the client pays through the partner's payment methods (Stripe, PayPal, bank transfer, etc.) — not through those of the hosting studio.

Passes and memberships

There is an important restriction for shared collaboration events: a client cannot use a pass or membership purchased from the hosting studio.

If an event accepts payment by pass or membership, the client must have a pass or membership directly with the partner studio — the studio that created the event.

Example: Studio A hosts classes from Studio B. A client has a credit pass at Studio A, but they cannot use it for Studio B's class. To pay with credits, they would need a pass purchased directly from Studio B.

If any of these payment methods are enabled on the event, a warning is displayed explaining that passes and memberships from the hosting studio cannot be used.

How bookings work

A booking on a shared event is always recorded under the partner studio, using the partner's payment methods.

The booking can happen either in the host's calendar (but the partner's pricing and payment methods apply) or directly in the partner's schedule.

In the public widget (on the studio's website)

If a client sees a shared event in the public widget on the hosting studio's website, the link redirects them to the partner studio's website (opens in a new tab). They complete the booking and payment directly with the partner.

In both cases, the booking and order are recorded under the partner, not the hosting studio. What the hosting studio can do with the shared event (view attendees, manage bookings, send a bulk message, edit the event, see statistics) depends on the permissions the partner studio has granted. The partner studio sets them with Edit permissions in Settings › Instructors and collaborations, in the Collaborations section; the hosting studio can check them there with View permissions.

Client data is not shared between the studios. If a client books through the host's schedule, they won't appear in the host's client list. Instead, they'll show up under the partner's clients, because they agreed to the partner's terms, payment conditions, and personal data policies.

Related articles

Did this answer your question?