Where events come from
Three source types, called "event types" throughout: Capable Event macros on pages; Confluence's own date chips on pages; and In-Calendar Events saved inside a Capable calendar. Page dates are read live out of the page every time a calendar renders.
#Where you do it
Task | Where |
|---|---|
Show the dates already on a page as a calendar | Page editor → insert "Calendar (Capable)" (Suite) or "Calendar macro (Capable)" (standalone) |
Point a page calendar at a shared, saved calendar | Calendar macro config → Content tab → Source |
Choose the view the macro opens in | Calendar macro config → Content tab → View |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Calendar subscriptions | Confluence settings → Capable (Capable Calendar in the standalone app) → Features | "Let users subscribe to Capable calendars from Google, Apple, or Outlook via a personal iCal feed. Turn off to disable subscriptions for all users." Only appears when the installed app includes the Calendar capability. T |
Calendar (global settings tab) | Confluence settings → Capable → Calendar | Card title "Calendar subscriptions", description "Personal iCal feed links your users have generated for calendars." Lists user, calendar, status and created date, paged with Previous/Next. Non-administrators see "Conflu |
Calendar capability visibility | Space settings → Capable → capability list → Calendar | Auto shows the byline where relevant. In the Suite that means only on pages Capable has already indexed as carrying dates. Always forces Calendar on for the space; Never hides it there. This is the generic per-capability |
#Worth knowing
The Base Timezone setting's own on-screen description tells users events are shown in the viewer's timezone.
#Limits that apply here
Pages where mentioned source
#Related
How it actually behaves.
