---
title: "Co-hosting — inviting another organizer onto your agenda"
description: "How to send and accept a co-host invitation, the agenda-only, revenue-sharing and all-to-the-host partnerships, how the split is calculated on the net amount, where to find your partnerships, and how to end one."
url: "https://vaidebaila.app/en-us/help/organizer/finance-and-refunds/co-hosting-invites-and-split"
lang: "en-US"
updated: "2026-11-11"
---

# Co-hosting — inviting another organizer onto your agenda

How to send and accept a co-host invitation, the agenda-only, revenue-sharing and all-to-the-host partnerships, how the split is calculated on the net amount, where to find your partnerships, and how to end one.

> [!NOTE]
> **This is done in the organizer dashboard**
>
> Open the dashboard at [dashboard.vaidebaila.app](https://dashboard.vaidebaila.app). The vaidebaila.app website is where the public buys tickets; managing your events happens in the dashboard. When a step happens somewhere else, such as the check-in app, the article says where.

## What co-hosting is

Co-hosting is a partnership between two organizers. One of them — the **host** — offers their
own public page so that the other organizer's events — the **guest**'s — show up there, in
front of the audience the host has already built.

The host chooses, when sending the invitation, how the sales of those events are split:

* **Agenda only (0%)** — no money is shared. The host receives nothing from the guest's sales;
  the guest keeps them as on any other event of theirs. It is a free listing on the host's agenda.
* **Shared (up to 90%)** — the host receives a share of every ticket sold on the events
  published to their agenda, and the guest keeps the rest.
* **All to the host (100%)** — the host sells the tickets of those events on **its own** payment
  account and receives all the money. The guest receives nothing through Baila.

In the first two cases the buyer pays through the **guest's** payment account, as on any other
event of theirs, and the guest stays responsible for the event, the payment-processing fees and
the refunds. In the third, the buyer pays the **host**.

Your agreement with Baila does not change because of this. In agenda-only and shared
partnerships Baila's fee stays exactly the same, and a host's share comes out of what is left
after it. In an all-to-the-host partnership the sale runs on the host's account, at the host's
own Baila rate.

## Agenda-only partnership (no commission)

Drag the bar to **0%** and the partnership is only about visibility:

* no money moves between the two organizers, and **no split is sent to the payment gateway** —
  the sale is charged exactly like any other sale of the guest;
* **neither side needs a payout account**, and the two do not need to use the same payment
  gateway;
* the invitation e-mail says so in its first line — *no commission* — and the terms state that
  no money is shared.

To start sharing revenue later, end the agenda-only partnership and send a new invitation with
a percentage. Events already published stay on the agenda with no commission until they finish.

## All-to-the-host partnership (100%)

Drag the bar all the way to **100%** when the guest runs the events but the money is the host's —
a school whose teachers publish their own classes, for example.

* **The host's payment account charges the buyer.** The host is the payee of the charge. No
  split is sent to the gateway for the guest.
* **Everything about the money is the host's:** Baila's fee (at the **host's** rate), the
  payment-processing fees, refunds and chargebacks.
* **The guest still runs the event** — creates it, edits it, checks people in, and is the one
  who cancels it or refunds a buyer. Those refunds are paid from the host's account.
* **What the host sees:** on the partnership page, the number of paid orders and the gross sales
  of each event. The host has no order list for these events and cannot issue refunds itself —
  ask the guest.
* **What each side needs:** the host's payment gateway must be ready to sell, with the webhook
  configured. The guest needs no payment account and no payout account.
* It applies to **all the sales** of an event published on that agenda, wherever the buyer found
  it — including on the guest's own page.
* An event published this way **cannot also share revenue with another host**. An agenda-only
  host can sit beside it.
* If the host's payment account stops working, tickets for those events **cannot be sold** until
  it is fixed. Sales never fall back to the guest's account.

Anything the host pays the guest for running the event is arranged between the two of them,
outside Baila.

The percentages between 91% and 99% are not offered: with so little left for the guest, the
payment-processing fees would not fit. The bar goes from 90% straight to 100%.

## Before you start a revenue-sharing partnership: register your payout account

> [!WARNING]
> For a partnership that **shares revenue**, **both sides** need a verified payout account: the
> host to send an invitation, and the guest to accept one. Without it the invitation is not sent
> and the acceptance cannot complete. An **agenda-only** partnership needs none of this — skip
> this section.

Go to **Integrations** (side menu, **Settings** group), open **Asaas** and, in the optional **Split revenue with co-hosts** section (at the bottom of the window), paste
your Asaas Wallet ID and click **Verify**. (The **Payments** page shows whether the account is
already verified and takes you straight to that spot.) We run two automatic checks and no charge is created for you.

If you see *"We couldn't confirm right now"*, that does **not** mean the account is wrong —
only that we got no answer. Try again in a few minutes.

If you see *"No gateway configuration found"*, what is missing is the step before this one:
save and validate your Asaas key in the same Asaas window, under Integrations, before verifying
the payout account. Verification uses your own key to prove the account is yours.

> [!NOTE]
> To share revenue, both organizers must use the **same payment gateway** (today, Asaas): the sale is charged on the
> guest's account and the host's share is split to the host's payout account in that same charge.
> If the gateways differ, the invitation or the acceptance is refused with that explanation.

Keeping the payout account verified is **not a one-time step**. If it stops working later, the
host stops receiving their share on the sales that follow — and that money is not recovered
afterwards. See *"If the host's payout account is not set up correctly, do they lose their
share?"* under the frequently asked questions.

## How to send an invitation

### Open Co-hosting

In the sidebar, under **Marketing**, click **Co-hosting**, then **Invite a co-host** (the same form also opens from **Invitations › New invitation**).

### Enter the organizer's e-mail

The invitation is identified **by e-mail**, and that address must belong to an organizer account
that already exists on Baila. If the person has no account yet, ask them to create one first.

### Choose how the sales are split

Drag the bar. It always shows both sides — how much is for you and how much the guest keeps:

* at **0%** it is an **agenda-only** partnership, with no commission;
* from **1% to 90%** it is a **shared** partnership, and the screen shows exactly how much each
  side gets on a R$100 ticket;
* at **100%** it is an **all-to-the-host** partnership: the guest's events are sold on your own
  payment account.

Under the bar, a short summary spells out the deal for the option you picked: who receives the
money, who charges the buyer, who pays processing fees and refunds, and what each side needs.

### Send it

The guest receives an e-mail that opens with the deal in one line and repeats who does what —
with the worked example when there is a split, calculated at the guest's own Baila fee, which
may differ from the one on your screen — and the invitation is valid for 30 days.

## How to accept an invitation

Click the button in the e-mail. You land on a page that states the deal in one line, shows who
does what and — when there is a split — the worked example, and then displays the **full text
of the terms**. Read it, tick **I have read and agree** and click **Accept invitation**.

The moment you accept, Baila records — and keeps permanently — who accepted, the server clock
and your browser clock, the IP address, the browser used, the exact text of the terms you saw
and a fingerprint (hash) of that text. This exists to protect both sides: either party can
later prove exactly what was agreed.

## How much each side gets — the R$100 example

This section is about **shared** partnerships. In an agenda-only partnership there is nothing to
calculate: the guest keeps everything. In an all-to-the-host partnership there is nothing to
split either: the host receives the sale, less Baila's fee at the host's rate and the
processing fees.

The host's percentage applies to the **net amount**, that is, to what is left **after** Baila's
fee.

| Step              | Amount      |
| ----------------- | ----------- |
| Ticket            | R$100.00    |
| Baila fee (10%)   | − R$10.00   |
| **Net amount**    | **R$90.00** |
| Host (15% of net) | − R$13.50   |
| **Guest keeps**   | **R$76.50** |

> [!NOTE]
> The host's percentage **never** applies to the gross amount. In the example above, 15% of gross
> would be R$15.00 — but the host receives R$13.50, because the figure is calculated on the
> R$90.00.

The 10% Baila fee in the example is used only to keep the arithmetic round. Your real rate is
usually lower — at 3%, for instance, the same 15% partnership works out as: net R$97.00, host
R$14.55, guest R$82.45. The real figure always appears on the invitation screen and in the
e-mail the guest receives.

> [!NOTE]
> The example is **before the payment gateway's processing fees** (Pix, card, installments). Those
> fees, like refunds and chargebacks, are the **guest's** and come out of the guest's part. On a
> sale where those fees do not fit in the guest's part — a high host percentage on a sale in
> many installments, for instance — the host's share **on that sale** is reduced by what is needed
> for the payment to go through. Baila works this out from the gateway's published fees (or a
> conservative estimate when they are not available), so the reduction can be slightly larger than
> the exact shortfall; with several hosts on one event it is divided between them in proportion.
> This is written in the terms both sides accept.

> [!WARNING]
> While you are composing the invitation, the Baila fee shown on your screen is **yours**. The
> guest's may differ, and theirs is the one that applies at the time of sale — which is why the
> e-mail and the acceptance screen always show the guest's real rate.

## The split applies only to events published on the host's agenda

When you create an event, you choose where it appears. There are three situations:

* **Only on your agenda** — no share goes to the host.
* **Only on the host's agenda** — the event appears on their page and **not** on yours, and the
  split applies.
* **On both** — the event appears in both places, and the split applies.

With an agenda-only partnership the same three choices exist, and no share goes to the host in
any of them — the selector shows that agenda as *no commission*.

With an all-to-the-host partnership, publishing the event on that agenda — alone or together
with your own — means **all** its sales go to the host. The selector says so next to the agenda's
name, and publishing is refused if you combine that agenda with another one that takes a share.

Events that stay on your own agenda never pass anything to the host.

## Choosing the agenda when you create an event

The selector appears on the last step of the creation wizard, next to the publish button, and
only if you hold at least one active partnership. If you have a partnership and choose nothing,
publishing is refused — this is a decision that has to be made on purpose.

Events created **before** the partnership existed stay on your agenda only. Nothing is moved
retroactively.

If you try to publish to an agenda whose partnership has already ended, publishing is refused
with the message *"This partnership is not active"*. That is deliberate: a warning you can act
on beats a publish that looks like it worked and put the event nowhere.

## Where to find your partnerships

Under **Co-hosting** you see every partnership, from both sides: the ones where you are the
host and the ones where you are the guest. You can filter by role.

Opening a partnership shows the agreement with its frozen figures, the full acceptance
evidence, the list of events published to that agenda, and the ending panel.

## How to end a partnership

> [!WARNING]
> Nobody ends it alone. One party requests and the **other** must confirm.

Whoever made the request cannot confirm their own. If you asked to end the partnership and see
no confirm button, that is not a fault: the other party is always the one who confirms, and that
is exactly what guarantees both sides agreed. Trying anyway returns *"The other party must
confirm the cancellation"*. While a request is pending nothing changes: the requester can
withdraw it, and the other party can decline it.

Once the ending is confirmed:

* events **already published** stay on the host's agenda **on the same terms** — the same split,
  no commission, or all sales to the host, still on the host's account — until they finish;
* **new** events can no longer be published to that agenda.

This also holds for people who already bought tickets: nothing changes for the buyer.

## Frequently asked questions

**Can I change the percentage later?**
No. The percentage is the agreement. To renegotiate, end the current partnership and send a new
invitation — events already published keep the old percentage.

**Can I have more than one host?**
Yes. You can hold several active partnerships at once and choose, event by event, which agendas
it appears on. The hosts' percentages add up, and together they cannot take more than 90% of an
event's net amount — agenda-only partnerships count as zero. An all-to-the-host agenda cannot
be combined with another agenda that takes a share.

**In an all-to-the-host partnership, who does the buyer pay?**
The host. The charge is created on the host's payment account, so the host is the payee of the
charge, even though the event page shows the guest as the organizer.

**Does an agenda-only partnership cost the guest anything?**
No. Nothing is passed to the host and nothing extra is charged. The guest pays Baila's fee and
the processing fees exactly as on any other event.

**What if the split fails at the gateway?**
This only concerns shared partnerships — agenda-only and all-to-the-host partnerships send no
split to another organizer. The sale is
**never** blocked because of it. The ticket is issued normally and Baila's fee is
still charged. What is lost is the host's share of that sale.

**If the host's payout account is not set up correctly, do they lose their share?**
They do — which is why it is worth checking before the first ticket is sold. The host's share is
paid out by the gateway at the moment of purchase, straight into their payout account. If that
account is not verified, or the gateway rejects it, there is nowhere to send the money: **it stays
in full with the guest organizer**. Baila never holds that difference at any point, so there is
nothing for us to refund or pass on afterwards.

When this happens we mark the payout account as *Needs attention* and e-mail the host with the
reason the gateway returned. From then on we **stop trying**: the sales that follow go through
without their share until the account is verified again. Verifying it again only counts from that
moment onward — sales made while the account was broken are not recalculated and not recovered
automatically. If it does happen, settling that period is between the two organizers.

Nothing else is affected: the partnership stays active, the events stay on their agendas, and
tickets keep selling normally.

**What happens to an event that is already live?**
Nothing. Its agenda and its split stay exactly as they were.
