# Non-staff members cannot create calendar events **URL:** https://meta.discourse.org/t/non-staff-members-cannot-create-calendar-events/376796 **Category:** Bug **Tags:** events **Created:** [July 31, 2025, 11:29pm UTC](https://meta.discourse.org/t/non-staff-members-cannot-create-calendar-events/376796 "2025-07-31T23:29:20Z") **Posts on this page:** 1 **Showing post:** 11
### Author: ![kris.kotlarek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kris.kotlarek/32/176919_2.png) [@kris.kotlarek](https://meta.discourse.org/u/kris.kotlarek) #### Post date: [August 12, 2025, 2:21am UTC](https://meta.discourse.org/t/non-staff-members-cannot-create-calendar-events/376796/11 "2025-08-12T02:21:19Z")
I took another look and I think I know what is happening. The wizard to build an event is adding this `allowedGroups=trust_level_0` to the event for public events. In most cases, by default, everyone can see the `trust_level_0` group, but in your case, it is configured that only Group owners and moderators can see it. Something similar to my test instance: ![demo of visibility](https://global.discourse-cdn.com/meta/original/4X/5/2/3/523f1526a7028980124052ac62b52b183f52a354.png) Because `allowedGroups` is mentioned, permission is checked and `trust_level_2` members cannot “see” `trust_level_0`. I will work on fixing the wizard so that it is not adding “allowedGroups” for public events, as it is unnecessary. In the meantime, you have 2 options to fix this issue: 1. Remove allowedGroups by hand so your event should look like this: ```plaintext [event start="2025-08-12 09:49" end="2025-08-13 00:00" status="public" timezone="Pacific/Auckland"] [/event] ``` 1. Change the visibility of `trust_level_0` group to `logged on users`. You can do this on this page `/g/trust_level_0/manage/interaction` I will let you know once the fix to the event wizard is fixed. --- _[View the full topic](https://meta.discourse.org/t/non-staff-members-cannot-create-calendar-events/376796)._