Creation
Be sure to be a team admin, and in case you are self-hosting, have the `managed-event-types` operational feature flag turned on. When creating a team event-type, you will be getting the option to create a Managed Event like so:Management
Once the managed event-type is created, you will be able to set all the fields you want to manage as a team admin. You can distinguish fields that will be locked by team members by the “lock” icon next to the field label, like so:Assignment
A crucial part of a managed event-type is the assignment of team members, so managed event-types can be created on your behalf. Think of the managed-event you created as a team admin as an event template, that team members will get regular event types from it once they are assign to it. Whenever you make changes to locked fields, every team member will also get the same change on their regular event type created upon this managed event-type. Note that unlocked fields will not have any effect on already created event types for assigned members, only for new assign members.Slug conflicts
When you assign a managed event type to a team member who already has a personal event type with the same URL slug, a confirmation dialog appears asking whether you want to proceed. If you confirm, the member’s personal event type is not deleted. Instead, it is:- Hidden from their public booking page so it no longer accepts new bookings.
- Renamed with a
-personalsuffix (for example,/consultationbecomes/consultation-personal) so the managed event type can take over the original URL. - Preserved with all of its existing bookings and settings intact. The member can still find it on their event types page.
The member receives an email notification explaining that their booking link has been replaced by a managed event type and that their original event type has been hidden.