Submission Settings
The Who can create events card controls who can create events on your site and how new events enter the system: whether they go live immediately or require admin approval first.
Go to Eventonomy → Settings → Setup and find the Who can create events card. (This was its own Submission tab before the settings screen was consolidated into seven tabs; the old ?tab=submission link still resolves here.)
What You Will Learn
- How to restrict event creation to specific WordPress roles
- How the approval mode moderation queue works (the Moderation inbox)
- How to set the default status for new events
- How to cap the number of events per user
Settings Reference
Minimum Role to Create Events
Setting: creator_role
Default: None (any logged-in user)
Choose a minimum WordPress role (Subscriber, Contributor, Author, Editor, Administrator) that a member must have to create events. Leave blank to allow any logged-in user.
This works alongside Eventonomy's own evnm_create_events capability. After you set a role, only members of that role or higher can access the event creation form on the frontend.
Note: Administrators always retain the ability to create events regardless of this setting.
Require Approval Before Submitted Events Are Published
Setting: approval_mode
Default: Off
On the settings screen this is New events from members, with two choices: Publish immediately and Hold for my approval. It is the one control for moderation.
When on, events submitted by members go into a Pending review queue instead of publishing immediately. Review them in the Waiting for approval tab of the Moderation inbox (Eventonomy → Moderation), which also lists member reports. Each event has Approve and Reject actions.
- Events you create yourself as an admin are unaffected and publish at the status you set.
- Members who can edit other members' events (
evnm_edit_others_events, held by Editors and Administrators by default) skip the queue and publish directly. See Capability map. - When approval mode is on, the event editor shows "Submit for review" instead of "Publish" for everyone else. Their submissions are forced to Pending review, including a submission that does not pick a status explicitly. An explicit Draft is still honoured, so members can park work in progress without entering the queue.
Note: The approval result email (approved or rejected) is sent to the organizer when you take action on a pending event.
Status When No Choice Is Made
Setting: default_event_status
Default: draft
Options: Draft, Published
The status an event gets when it is created without choosing one, for example through the REST API or the mobile app.
- In the event editor, members choose Publish event or Save draft themselves, so this setting does not apply there.
- To review members' events before they go live, turn on Require approval above. That is the one control for moderation; with it on, members see Submit for review instead of Publish event.
- Earlier versions also offered Pending review here. Sites that had chosen it are switched to Require approval on update, so their members' events keep waiting for review.
Max Events Per User
Setting: max_events_per_user
Default: 0 (unlimited)
Limits how many events a single member can create. When a member reaches the limit, the create form shows an error message and the event is rejected.
Set to 0 for unlimited. Admins are not subject to this limit.
Pro - A per-role capability matrix that controls what each role can see and do across the event lifecycle is available in Eventonomy Pro.
What's Next?
Configure the RSVP system: capacity, guests, deadlines, and waitlists.