Update documentation

docs/guides/community-dashboard.md

@@ -96,7 +96,7 @@ Key sections include:
 - General Settings.
 - Branding.
 - Social Links.
-- Advertisement (coming soon on the public site; not displayed yet).
+- Advertisement.
 - Additional Content.
 
 Common use cases:
@@ -106,6 +106,10 @@ Common use cases:
 - Maintaining logo, banner, and Open Graph preview assets for consistent presentation.
 - Managing social links, optional ad placements, gallery images, tags, and extra links.
 
+Advertisement settings are community-wide. When a banner image is configured, OCG shows it on the
+public community page and as a floating banner on public group and event pages for that community.
+The optional banner link URL makes the banner clickable.
+
 Field requirements, character limits, and list limits are shown inline in the settings UI.
 
 ![Community settings area](../screenshots/dashboard-community-settings.png)

docs/guides/event-operations.md

@@ -220,15 +220,20 @@ whole linked series, but editing event content is intentionally one event at a t
 
 ![Event date and venue](../screenshots/dashboard-group-event-date.png)
 
-### Hosts and Speakers
+### Hosts, Speakers, and Organizers
 
 In this tab, you manage event-level people and sponsor attribution:
 
 - Add hosts from any user account on the site.
 - Add visible speakers/presenters.
 - Attach event sponsors from reusable sponsor records.
 
-This is where attendees understand who is running and presenting the program.
+OCG also shows an `Organizers` section on the public event page. Organizers are snapshotted from
+the accepted group team when the event is created, so later group team changes do not rewrite
+existing event attribution. Use event hosts for people who should be explicitly highlighted as
+running the event program.
+
+This is where attendees understand who is running, organizing, and presenting the program.
 
 ![Event hosts and speakers](../screenshots/dashboard-group-event-hosts.png)
 
@@ -397,13 +402,19 @@ This tab supports delivery-day execution:
 - Review attendee list and RSVP timing.
 - Run manual check-in.
 - Generate check-in QR code for on-site flow.
+- Cancel confirmed free attendance for future active events.
 - Invite attendees to free RSVP events.
 - Send attendee-wide operational emails.
 - Download the attendee list or attendee answers as CSV.
 
 Manual check-in bypasses attendee self-check-in timing windows, but the person must already be
 registered as an attendee and the event must still be published or active.
 
+`Cancel attendance` is available from confirmed attendee row actions for future, active events
+when the attendee does not have a paid ticket. OCG removes the attendance, notifies the attendee,
+and can promote the next waitlisted user when a seat opens. Paid attendees stay on the refund
+workflow instead.
+
 `Invite` is available for free RSVP events when you have event write access. You can select a
 registered platform user or enter an email address. For email invitations, the address must match
 the invitee's LF account primary email because they must log in with LF SSO to accept. Pending

docs/guides/user-dashboard.md

@@ -45,12 +45,14 @@ Each row includes:
 - Event title with a direct link to the public event page.
 - Event location.
 - Event date and time.
-- Your role in that event (`Attendee`, `Registration pending`, `Host`, `Speaker`, or multiple
-  roles).
-
-When a row is marked `Registration pending`, use the row actions menu to complete the event's
-registration questions. You can update submitted answers from the same menu before the event
-starts.
+- Your participation roles in that event (`Attendee`, `Host`, `Speaker`, or multiple roles).
+- Your attendance status when action is still needed, such as `Payment pending` or
+  `Registration pending`.
+
+When a row is marked `Payment pending`, use the row actions menu to complete checkout while the
+ticket hold is still active. When a row is marked `Registration pending`, use the row actions menu
+to complete the event's registration questions. You can update submitted answers from the same
+menu before the event starts.
 
 Filtering behavior: