Deleting an event safely

Edited

Overview

Deleting an event removes it from your dashboard, the public storefront, and all reports. Chamberly blocks deletion if the event has active orders to protect your sponsors and your records. This article explains the safe path.

Before you start

  • You need an org_manager role to delete events

  • Confirm the event has no active orders (Sales > Orders, filter by event)

  • Consider archiving instead — archived events are hidden but data is preserved

Step-by-step

  1. Open the event from Sidebar > Events

  2. Click Edit event

  3. Scroll to the bottom and click Delete event

  4. Read the confirmation dialog — it lists what will be removed

  5. Type the event name to confirm

  6. Click Delete permanently

What gets deleted

  • The event record

  • All sponsorships on the event

  • All sponsorship benefits

  • First-rights holder assignments for this event

  • The public event page

What is preserved

  • Orders are blocked from deletion — you must cancel or refund first

  • Sponsor accounts and their other purchases remain untouched

  • Email log entries reference the deleted event by name only

Tips & best practices

  • Almost always prefer Archive over delete — you keep historical reporting and can un-archive later

  • If you must delete because the event was created by mistake, do it before any orders come in

  • Take a screenshot of the event configuration before deleting in case you want to recreate it

FAQ

Can I undo a delete?
No. Deletes are permanent. If you might want it back, archive instead.

What if the event has cancelled orders only?
You can delete it. Only active and paid orders block deletion.

What if I just want to hide it from the public?
Set the status to draft or archived instead of deleting.

Related articles

  • Event statuses (draft, active, archived) explained

  • Editing an event

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.