Public Pages
Public pages are the read-only viewing and sharing layer of RoleSchedule. People can check published schedules without dashboard access, and group or member schedules can stay subscribed in Google Calendar through a live calendar feed.
Use this guide when you need to
- Share organization, group, and member schedule views without exposing dashboard tools.
- Let group and member viewers subscribe to a live schedule feed in Google Calendar.
- Use exports and stable links instead of sending new screenshots every time the schedule changes.
Jump to section
Purpose
Give viewers the schedule without giving them the dashboard
- Provide fast schedule visibility outside the protected scheduling workspace.
- Give members and groups a stable schedule link they can return to throughout the week.
- Let viewers subscribe to supported public schedules in Google Calendar without repeatedly importing new files.
Workflow
Publish once, then share the right viewing layer
- Publish the schedule from the dashboard once the week is ready for viewers.
- Share the organization page for broad awareness, the group page for team-level visibility, or a member page for an individual schedule.
- For group or member schedules, use Sync to Google or copy the calendar feed URL when someone wants the schedule in their calendar.
- Return to the dashboard for edits; public pages and subscribed calendars are the viewing layer, not the planning layer.
Calendar sync
Subscribe once, then let schedule changes flow into Google Calendar
RoleSchedule exposes a live calendar feed for public group and member schedules. A viewer can choose Sync to Google once, and Google Calendar remains subscribed to that feed instead of requiring a fresh calendar file every time the schedule changes.
Calendar subscriptions refresh on Google’s schedule, so a newly published change may take some time to appear in Google Calendar. The viewer does not need a new RoleSchedule link or another manual import.
See public schedule sharing features- Use Sync to Google directly from supported public group and member schedule pages.
- Copy the feed URL when another calendar app needs a subscription link.
- Published schedule changes remain available through the same feed URL.
- Keep planning permissions inside RoleSchedule while giving viewers a familiar calendar experience.
Web view or calendar?
Use the public page for context and the calendar feed for daily habit
The public page is the best place to inspect the current published week, group context, and schedule details. A subscribed calendar is better for someone who wants assignments to appear alongside the rest of their day without repeatedly opening RoleSchedule.
Both point back to the same published scheduling workflow. The difference is how the viewer consumes it.
- Leader checking the whole team → group public page.
- Member checking personal duties → member public page.
- Member who lives in Google Calendar → subscribe once to the live feed.
Guidance
Choose the delivery method that matches how people consume the schedule
Some viewers want a quick web page. Others live in Google Calendar. RoleSchedule supports both without turning read-only users into workspace editors.
Choose the public view that matches the audience
Organization public pages are useful when leaders want a top-level view. Group public pages are better when someone only cares about one platoon, section, or team. Member public pages are best for a single person who needs a focused weekly schedule without parsing the entire organization.
Use calendar sync when the viewer lives in Google Calendar
A public web page is ideal for checking the latest schedule on demand. Calendar sync is better for someone who already organizes their day in Google Calendar. The subscription keeps pointing at the same RoleSchedule feed, so published changes can flow into the calendar automatically as Google refreshes it.
Use exports when you need to distribute many links at once
Public pages become more useful when links are easy to distribute. Export-by-name actions reduce copy-and-paste mistakes when leaders need a group-level link plus individual member links for a larger roster.
Keep public pages intentionally simpler than the dashboard
Public pages should answer a small set of questions quickly: what is this team working, what am I working, and what changed in the published schedule. Editing, requirements, Auto-fill, permissions, and other planning controls stay in the protected workspace.
Practical notes
Sharing practices that reduce repeated schedule questions
- Use the member schedule link when a person only needs their own assignments and calendar subscription.
- Tell viewers that Google controls calendar-feed refresh timing; they do not need to unsubscribe and re-add the feed after normal schedule changes.
- Keep display names polished because they appear in public pages, exports, and calendar event context.
- If a viewer needs editing power, give them the appropriate workspace access instead of expanding the public page into a second dashboard.
Questions
Questions viewers actually ask about shared schedules
Login requirements, Google Calendar subscriptions, refresh behavior, and choosing the right public view.
Do people need a RoleSchedule account to view a public schedule?
No. Public schedule pages are specifically meant for read-only viewing without giving someone dashboard access or editing permissions.
Can members sync their RoleSchedule schedule to Google Calendar?
Yes. Supported public member and group schedule pages provide a Google Calendar subscription backed by a live calendar feed. The viewer subscribes once and continues using the same feed as published schedules change.
Will Google Calendar stay up to date when the RoleSchedule schedule changes?
The subscription keeps pointing to the same live RoleSchedule feed, so newly published changes are available without re-importing a file. Google controls how often subscribed calendars refresh, so changes may not appear instantly.
Should I share a group page or an individual member page?
Use a group page when someone needs team-level context and a member page when the person only needs their own published duties. Someone who lives in Google Calendar can subscribe to the supported member or group feed instead of repeatedly opening the web page.