> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.cal.id/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Managed Events

Managed event types let team admins create common event types for members and manage them from one place. Some fields are **locked** by the admin; others stay open for members to edit.

> **Note:** Managed Events v2 doesn't yet support Webhooks and Apps — those are planned for later releases.

| Create a managed event

You must be a team admin (and, if self-hosting, have the `managed-event-types` feature flag on). When creating a team event type, choose **Managed**.

![](https://storage.crisp.chat/users/helpdesk/website/-/6/f/1/c/6f1c2c7b8034d000/image_1fzris0.png =1168x615)

![](https://storage.crisp.chat/users/helpdesk/website/-/6/f/1/c/6f1c2c7b8034d000/image_uyidlv.png =1168x615)

| Manage locked fields

Once created, set the fields you want to control as admin. A **lock** icon next to a field label marks it as locked for members.

![](https://storage.crisp.chat/users/helpdesk/website/-/6/f/1/c/6f1c2c7b8034d000/image_15340qp.png =1168x615)

| Assign to members

Think of the managed event as a **template**: assigned members each get a regular event type based on it.

* Changes to **locked** fields propagate to every assigned member's event type.
* Changes to **unlocked** fields only affect newly assigned members, not existing ones.
* If a member already has an event type with the same slug, you'll be prompted to confirm — the conflicting event type is deleted and replaced, and the member is notified by email.