> For the complete documentation index, see [llms.txt](https://products.monterosa.co/mic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://products.monterosa.co/mic/creator-guide/events.md).

# Managing Events

Events are time-bound containers for interactive live or on-demand content

## What is an Event?

An Event could be a campaign, a game, a show or any duration of time that you choose.

<figure><img src="https://2539678054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq9pQqNk9IovpAN9EXqbX%2Fuploads%2FJG74yT0KLbQvKXYCTmrw%2FStudio%20-%20Events.png?alt=media&amp;token=e952e9de-f5e7-41e6-9bd0-6f34d9a7c936" alt=""><figcaption></figcaption></figure>

## How do I find an Event?

Events are categorised into three status types:

<table data-header-hidden><thead><tr><th width="163.39312744140625"></th><th></th></tr></thead><tbody><tr><td><strong>Now &#x26; Next</strong></td><td>Events that are currently live, waiting to be manually started, or scheduled to start at a clock time. The event types are <code>live</code> <code>manual</code> or <code>upcoming</code></td></tr><tr><td><strong>Finished</strong></td><td>Events that have been completed or stopped</td></tr><tr><td><strong>Repeats</strong></td><td>Events that are set to repeat</td></tr></tbody></table>

You can also search for Events using the Event's name or UUID.

## How do I create an Event?

Click on the ***+ New Event*** button on the *Events* screen. Give your Event a name, a start time (manual or scheduled) and duration.

<figure><img src="https://2539678054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq9pQqNk9IovpAN9EXqbX%2Fuploads%2FcbrShvbPSzmBaCeP32Zc%2Fimage.png?alt=media&amp;token=281d78ca-5de9-4401-9e40-a08d15604a69" alt=""><figcaption></figcaption></figure>

## How do I schedule an Event?

When creating an Event select the `Scheduled` option as the start mode. Next, you can indicate the `start time` of your Event and the end mode. The end mode can also be `Scheduled` with an `end time` or after set duration of time.

<figure><img src="https://2539678054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq9pQqNk9IovpAN9EXqbX%2Fuploads%2FseryRWXaZDnHF8bV6xys%2Fimage.png?alt=media&amp;token=1995ebbd-7fe5-43d9-bcdb-1492c99eb919" alt=""><figcaption></figcaption></figure>

## How do I repeat an Event?

When scheduling an Event simply select the `Repeat Event` checkbox at the bottom of the New Event menu.

## Can I clone an Event?

Yes, there are two destinations for the cloned Event, it can be cloned into the same Project or a different Project.

### How do I clone an Event into the same Project?

To clone and edit an Event simply go to the menu button as shown below and choose `Clone & Edit` and a new Event will be created within the same Project.

<figure><img src="https://2539678054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq9pQqNk9IovpAN9EXqbX%2Fuploads%2Ft3iSSH1PjatBQYKxeKGV%2Fimage.png?alt=media&amp;token=06081b85-55e2-4474-8cef-c0106035a942" alt=""><figcaption></figcaption></figure>

### How do I clone an Event into a different Project?

If you want to create a copy of an Event into another Project, use `Clone Into` then select the Project. Note that you must have full access to the other Project you want to drop the duplicated Event into.

{% hint style="info" %}
Cloning an Event works only between Projects that share the same App.
{% endhint %}

## Can I create an Event Template to be reused?

If you have a repetitive use case, you can create an [Event Template](/mic/creator-guide/events/event-templates.md). To create one, simply click on the ***menu*** icon at the end of the Event row and then select *Create Event Template*. Once created the template will be stored in [Event Templates](/mic/creator-guide/events/event-templates.md).

## How do I find the Event ID?

When inside an Event the Event ID can be viewed and copied on hover of the Event title in the breadcrumbs. Click on the # icon which appears next to the Event title and the Event ID becomes visible with the option to copy it.

<figure><img src="https://2539678054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq9pQqNk9IovpAN9EXqbX%2Fuploads%2FrNDuVI29WKQc7pRJvkCI%2FStudio%20-%20Event%20ID%20-%20URL.png?alt=media&amp;token=0b1823bd-993e-4b39-a7e9-340a1d3a92e7" alt=""><figcaption></figcaption></figure>

## Which Event is displayed in the Fan UI when embedding using the Project ID?

When an Experience is embedded using a Project ID instead of a specific Event ID, the **most recently published live** Event will be shown in the Fan UI.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://products.monterosa.co/mic/creator-guide/events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
