# Submitting an event for review

Understanding the event status flow from Draft to published.

> Source: https://help.nyebar.id/en/organizer/managing-events/submitting-an-event-for-review

Once your event is ready, the next step is to submit it for review so it can be published. This page explains the status flow and what you need to prepare.

## Event status flow

Events on Nyebar go through several statuses (the same ones as the filters in the event list):

- **Draft** — you're still working on the event and it isn't visible to the public yet.
- **In Review** — you've submitted the event and the admin team is checking it.
- **Active** — once approved, the event is published and potential attendees can access it.
- **Ended** — an Active event is automatically considered ended once the event time is over. There's no button to press or anything you need to do.
- **Rejected** — the event didn't pass review; fix the details, then submit it again.

## Submitting your event

1. Make sure all the event details are complete and **at least one ticket type isn't hidden** (it's Active or Paused). This is required before you can submit.
2. On the event page, click the **Submit for Review** button.
3. In the **Submit Event for Review?** dialog, read the note about which details will be locked after publishing, then **tick the checkbox** to agree to Nyebar's Terms & Conditions and Privacy Policy.
4. Click **Yes, Submit for Review**. This button only becomes active after you tick the checkbox.
5. Wait for the admin team to approve the event. Once approved, the event automatically becomes **Active** and is visible to the public.

> **Details are locked after publishing**
>
> The submission dialog reminds you that the event's main details (title, poster, description, category, time, and location) can no longer be changed once the event is Active. Check everything one more time before you agree and submit.

> **No ticket types yet?**
>
> If the event doesn't have any ticket types, you'll see a **Create a Ticket Type First** reminder. Create at least one ticket type in the **Tickets** tab before submitting the event. If every ticket type is **Hidden**, you'll see an **All Tickets Are Hidden** reminder. Change at least one ticket to Active or Paused first.

> **After the event takes place**
>
> Once the event time is over, the event automatically becomes **Ended** and the full post-event withdrawal opens right away — no need to mark anything.

> **What's checked during review**
>
> The review makes sure your event is complete and follows the platform's terms. Events with clear, well-organized information help the process go smoothly.

> **Complete everything before submitting**
>
> Check all the details again before submitting so you don't have to fix and resubmit. Review times can vary, so submit well ahead of your event date.