Teams and round robin

Make a team

Open Teams in the sidebar and press Create team. Give it a name and a page address: the team’s page is at /team/<address>, and its event types are at /team/<address>/<event-type>. You become its owner. A team can have up to 25 people, counting invitations still waiting.

Invite people

Enter an email address and a role under Invitations. The person gets an email with a link that works for seven days and only for the address it was sent to, so a link that leaks can’t be used to get in. You are also shown the link to send yourself. They sign in (or sign up) with that address and press Join. A member needs to have finished setting up their account, with hours and a username, to be offered bookings.

• Owner: everything, including changing roles and deleting the team. A team always keeps at least one.
• Admin: invites members, removes members, and makes and edits event types.
• Member: takes bookings, and can see the team, its members and its event types. A member can leave at any time.

Team event types

A team event type has the same settings as your own (length, questions, buffers, limits, location) plus a list of hosts, the members who can take its bookings. Group sessions aren’t available on team event types yet.

Who gets a booking

A time is offered when at least one host is free then. Each host’s own default hours, existing bookings and connected calendars decide when they are free, so nobody is double booked and no one has to share their calendar with the team. When someone books, CalFree picks, from the hosts free at that time, the one with the fewest meetings still to come on that event type. A tie goes to whoever was given a booking longest ago. The meeting is then an ordinary booking for that member: it goes on their calendar, with their Zoom, Meet or Teams link, and they get the emails and webhooks.

A member who has blocked the invitee’s address is never given the booking. A member whose calendar can’t be read at that moment is left out of that search, and the others are still offered.

Rescheduling keeps the booking with the same member, so only their free times are shown. Cancelling frees their time as usual.

When someone leaves

A member who leaves, or is removed, comes off the team’s event types. An event type left with no host is turned off. Meetings they already have stay with them. Closing an account is refused while the person is the only owner of a team that has other members.

With the API

Anyone can list slots for a team event type and book it with the public routes of the REST API, using its id. API keys and the MCP server work on your own event types; team event types are managed in the dashboard for now.