This article explains how to share Schedule Requests on a public-facing webpage by embedding a Public Event Calendar from the Schedule Requests module as an iframe. It’s designed for teams who want community members to view events without exposing internal-only details.SummaryA Public Event Calendar lets you publish a schedule-requests-only calendar for external viewers (for example, parents, community members, or renters). When you publish the calendar, you choose:Which Schedule Requests are included (request types, statuses, buildings)Which event details are visible to the publicSetup InstructionsTo publish a public event calendar, your user type must have Can publish event calendar enabled.If you don’t see the Publish event calendar option, an FMX Administrator (or anyone with Admin Settings access) can enable it:Go to Admin Settings > User TypesEdit the user type for the people who should be able to publishEnsure the following user type permissions are selected within your Schedule Request Access section (your organization’s Schedule Request module may be named differently)Can publish event calendars = CheckedRead (approved & accepted) = Any or Accessible buildings (users set to Own will not be able to publish event calendars)OPTIONAL: Read (unapproved & unaccepted) = Any or Accessible buildings (only if intending to publish these types of events)NOTE: For this version of the iframe, you don’t configure access through a Public Access/Anonymous user type. Instead, you control what the public can see when you publish the calendar (request types, statuses, buildings) and by choosing which fields are visible on thumbnails and in the event details.Creating a New Event CalendarNavigate to “Schedule Requests” (your module might be named differently)Click “Event calendars” on the top right of the screenClick “New event calendar” at the top right of the screen (this opens a 3-step wizard)Step 1: General SettingsProvide a name for the calendar that will display anywhere this calendar is usedSelect which request types to include, or leave it empty to select allSelect which statuses to include, or leave it empty to select allSelect which buildings to include, or leave it empty to select allSelect which embed size you would like to useNOTE: Only request types and buildings available to the publishing user will be available to select from the drop-downs. Leaving any dropdown empty will select all of that type, but still be limited to what the publishing user can access.Step 2: Field VisibilitySelect which location fields you would like included in the thumbnail of each event (what you see from the calendar itself before clicking on an event)Select which fields you would like to be displayed when opening an event from the calendarNOTE: The event name (including ID, if in use), date, and time will always be displayed in the thumbnail and when opening the event. These cannot be hidden.Step 3: Copy iFrame CodeCopy the provided code to place anywhere you like (such as your organization website)You may also highlight and copy just the source URL (the URL that follows after iframe src=, not including the quotation marks) to provide a direct link to this calendarNOTE: You can use the direct link method described above to preview your published calendar.Updating and Deleting Event CalendarsNavigate to “Schedule Requests” (your module might be named differently)Click “Event calendars” on the top right of the screenTo delete an event calendar, click the “…” action button on the desired event calendar, then select “Delete”To change an event calendar, click the “Edit” action button on the desired event calendar, then follow the same wizard used during creationTo view changes made to an event calendar, click the “…” action button on the desired event calendar, then select “Audit Log”NOTE: All changes made to an existing calendar’s name, filters, and field visibility will be applied immediately, without having to change the iFrame code. If a new embed size is selected, a new code will be generated that must be copied and placed in all published locations. Was this article helpful? 1 out of 1 found this helpful