Events gives a community one place to coordinate scheduled moments such as planning sessions, workshops, demos, larger meetings, and shared deadlines. It keeps the date and expected attendance easy to scan while giving every event enough room to explain why people should join.

Events belongs to the area where the occasion is organized. A space can host community-wide events, while a subspace or activity can keep a more focused schedule close to the people and work it concerns. This makes Events a shared coordination tool rather than a personal calendar.

A Card For The Plan, An Article For The Story

An event first appears as a card. Active cards bring the essential decision-making information together: the schedule, title, author, attendance responses, and signals from the related discussion. Members can understand what is coming and respond without opening every event.

The card is deliberately concise. Selecting it opens the event's linked article, where the author can provide an agenda, preparation notes, links, background, and follow-up material. Comments, reactions, Awards, linked posts, and linked articles keep the conversation and supporting work attached to the occasion.

The card and article are two views of the same event. Changes to the title, keywords, or schedule remain aligned between them, so a date shown in the Events list does not become disconnected from the detailed page. This pairing is especially valuable across the event lifecycle:

The event article keeps the schedule and invitation context together before, during, and after the occasion.

Event Articles explores this relationship in more detail.

Events Follow The Community Structure

Opening Events shows the events for the current community area. The chosen scope keeps a focused workshop from being presented as a commitment for the entire community:

Published events can also surface beyond the main Events list. An area's About page may highlight a small selection of events with strong confirmed or tentative interest, while Search can help members find published events across spaces they have joined. Wherever a member discovers an event, opening it leads to its linked article.

Choosing the right area is therefore both an organizing and an access decision. A reader must be able to access that space area to browse the event, open its details, or respond to attendance.

Active And Completed Events

Events separates occasions by whether their end time has passed. Active events include upcoming and ongoing occasions. They use full cards because schedule and attendance decisions are still relevant. Once an event ends, it appears under Completed Events in a more compact form.

Completed does not mean discarded. The card remains a route back to the event article, its author, its attendance picture, and its community discussion. This continuity makes Events useful as a memory of what happened, not only as a list of what comes next.

The schedule also becomes more stable as time passes. A future event can have its start and end updated. After it begins, its start is fixed while an eligible editor can still adjust the end. After completion, the full schedule is locked so the historical record does not quietly change.

Active events keep schedule and attendance prominent, while completed events remain compact routes back to their context.

For the practical editing flow, see Update Event Details and Schedule.

Draft Privately, Publish When Ready

New events begin as private drafts. Only the current author sees those drafts in a separate view, where they can reopen unfinished work and continue preparing the title, keywords, schedule, and article content. The draft stays out of the community's published event list until the author publishes it.

This private stage gives an organizer room to turn a date into a useful invitation. A clear article can answer the questions that influence attendance: what the session is for, who should join, whether preparation is needed, and what participants can expect afterward.

Publishing joins the event card and article into the visible experience for eligible area members. Later edits continue to update both views. Deleting an eligible event removes the event and its linked article together, so members are not left with a detail page that no longer has an event behind it.

Follow Create and Publish an Event when you are ready to take an event from private preparation to a community-visible invitation.

Attendance Is A Shared Signal

Area members can respond to an active event without receiving event-management access. The card highlights the member's current choice and shows the totals for each response, giving organizers a practical estimate:

A response is not permanent. Selecting a different option replaces the earlier choice, and selecting the current option again clears it. This lets the attendance picture change as members learn more about their availability.

Attendance is useful guidance rather than a substitute for the event article. The counts show likely participation; the article explains what participants are confirming and what they need to know. See Attendance for the response states and their effects.

Access And Responsibility

Event authority follows the area and the person's relationship to the event. Joining a space does not grant blanket editing rights, and receiving authority in one scoped area does not automatically make someone an event manager everywhere.

The main boundaries are:

These distinctions let a community delegate event coordination without making every organizer a broad space administrator. They also protect private-area events: a role or authorship relationship does not make an event visible to someone who cannot access its area.

Useful Actions Around An Event

Event cards offer a small set of supporting actions. What appears depends on the member's access and the state of the event:

These options support discovery, appreciation, and curation, but they do not change the core ownership model. Saving an event does not affect other members, and social actions do not grant permission to edit its schedule or article.

For a discovery-focused journey, continue with Find and Follow Events.

A Continuous Record Of A Community Moment

Events stays coherent as an occasion changes. Publishing moves a prepared draft into the shared list. Title, keyword, and schedule updates remain visible on the card and article. Attendance changes update the shared picture for members viewing the same area. When the end time passes, the event becomes completed while its article and discussion remain available.

That continuity is the main reason to use Events for important community moments. Members do not have to reconstruct the purpose from a date alone, and organizers do not lose the outcome when the occasion is over. The schedule, invitation, participation signals, and follow-up context remain connected.

Common Questions

Is Events a personal calendar?

No. Events coordinates scheduled moments for a space, subspace, or activity. It does not organize an individual's private schedule.

Who can see an event draft?

Only its current author sees it in the draft view. It becomes available to eligible area members after publishing.

Why does every event open as an article?

The card keeps discovery and attendance quick, while the article provides the agenda, background, links, discussion, and follow-up that a simple schedule entry cannot hold.

Can every space member manage events?

No. A person needs ownership or applicable event-management access for management actions. Creating an event also requires Coordinator access, while ordinary members only need access to the event's area to respond.

What happens after an event ends?

It moves into Completed Events with a compact card. Members can still open the linked article and revisit its context and discussion, but the completed schedule is locked.

Can I change my attendance response?

Yes. Choose another response to switch, or choose the selected response again to clear it.

Does saving an event change its visibility?

No. View Later is personal. It helps you return to the event but does not publish it, move it, or make it visible to someone who lacks area access.