Edit event details and manage photos
Update a published event, preserve valid registration capacity and remove unwanted public photos.
This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.
Start here
- Open Existing Events and choose Edit beside the event you own or manage.
- Check the title at the top, then change the required details or attendance settings.
- If registrations exist, compare reserved places with Available places before reducing capacity.
- Use Add photos for new images or Remove photo in Current photos for an existing image.
- Choose Save changes for the main form, then Open public page to verify the result.
Open an event you can edit
The network owner can edit network events. A manager can edit only events owned by that manager, even if more events are visible through the hierarchy. Event not found or you do not have permission to edit it indicates the requested event cannot be opened in this account. Return to Existing Events and use a displayed Edit action.
Back to Existing Events and Cancel in the main form return to the list. They do not cancel the published event. The Cancel event-status action is on the event list and has a different purpose.
Update the published information
The form edits Title, Full description, Start date and time, End date and time, and Location or online link. The creation limits still apply: title 190 characters, description 20,000 characters and location 500 characters; the end must be after the start. Rich formatting and safe links are supported in the description.
Save changes persists the form and returns to the edit page. Open public page verifies what attendees now see. Changing the description or location affects the public event, so confirm any meeting links and timing before saving.
Change registration settings without losing capacity
Who can attend? chooses Open to everyone or Registration required. Available places must be between 1 and 100,000 when registration is required. Pending and confirmed requests count as active reserved places.
The site prevents disabling registration while active registrations exist and prevents lowering capacity below their total requested spots. Review requests on Existing Events first if the change is rejected. Changing the event’s capacity does not automatically decline attendees or reduce their requested spot counts.
Add or permanently remove photos
Add more event photos shows the number of slots already used. The event supports 12 photos total, in JPG, PNG, WEBP or GIF, up to 10 MB each. New uploads are added when the main form is saved. If the limit is reached, remove an existing image before adding another.
Current photos lists existing public images. Remove photo is a separate form and confirmation that immediately removes that image from the event and stored file. It is not saved with the main form. Save any text edits first if you are about to perform a separate removal, since the page reloads afterward.
If there are no photos, the page prompts you to use Add photos. A photo deletion cannot be undone from this page; upload the image again if you still have the original and need it restored.
Frequently asked questions
Does the Cancel button here cancel the event?
No. In the edit form it returns to Existing Events without submitting the form. Use the event list’s Cancel action to mark the event cancelled.
Why can I not reduce capacity to the number of forms?
Capacity counts requested spots, and a form may request multiple places. Pending and confirmed spot totals must fit the new capacity.
Why can I not turn registration off?
The site blocks that change when there are active registrations. Review the existing requests before changing the attendance model.
Are photo removals saved only when I choose Save changes?
No. Remove photo is a separate immediate action after confirmation. It reloads the page, so save unrelated form edits first.
Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.