Skip to main content

Calendar & events

Every space has a calendar, one of the standing surfaces on the space's desktop. Two kinds of thing show up on it: events the space puts on, and the space's posts, marked on the dates they were published.

Two kinds of event​

When a space creates something for the calendar, it's one of two kinds, and the kind is fixed once it's made:

  • An Event is something to show up to — meet, chat, or attend. It has a time and a format: a call link, an in-person venue, one of the space's chat rooms, or Other when it's none of those.
  • An Update is a heads-up that the space is going to publish something. Members are kept in the loop, and the organizer attaches the post once it lands.

Who does what​

Only a space's admins and owners create events — plus a group's own managers, for events on that group's calendar. The person who made an event, an admin, or a manager of the event's group can edit it. Everyone else takes part — you attend Events and follow Updates.

An event is live the moment it's created. When you make an Event you can tick Send a notification to all members (or to the group's members, for a group's event), and you're marked as going automatically — unless the event needs a ticket you don't hold.

Who can see an event​

Every event carries a visibility setting. You pick it when you make the event and can change it later, and it's the only thing that decides who finds the event on the calendar:

  • Members — everyone in the space. This is where most events sit, and it's the default.
  • Group — only the members of one group. Members of the space who aren't in that group never see it.
  • Admins only — just the space's owners and admins. Useful while something is still being planned.
  • Public — anyone can see it, signed in or not. A public event gets its own page on the space's public web address, so you can share it with people who have no DFOS account at all. The rest of the calendar stays members-only.

Only a space's owners and admins can make an event public, and only they can move an event between visibility settings at all; a group's managers can move their event between groups they manage. There's more on how public and private fit together in Who can see what.

Going to an Event​

On an Event, tap Attend and it becomes Going; tap again to change your mind. Once people are in, the Event shows who's coming — "N going," with faces. Updates don't take attendance — there's nothing to show up to yet. If you organized the Event, you get a notification when someone says they're going.

Anyone who can see the Event can open the full list of who's going. A space's owners and admins can also export that list with Export CSV, which includes attendees' email addresses — useful for a door list or a follow-up note. You'll get the file once it's ready.

Tickets​

A ticket is a product that admits its buyer to an Event. It's sold right from the event, and buying one marks you as going.

Selling tickets​

Space owners and admins can add tickets to an Event whose visibility is Members or Public. Updates, group events, and admins-only events can't carry tickets.

In the event form, under Event options, open the Tickets row:

  • Ticket name and Price — Free, Fixed price, or Pay what you want (with a minimum and an optional suggested price).
  • + Limit capacity caps how many can be sold. Leave it off for unlimited.
  • Require ticket means only ticket holders can RSVP. Turn it off to sell tickets while still allowing plain RSVPs.

Saving the event creates the ticket in your shop, with the event's description and cover. You can also sell a product you already have as the ticket, and an event can carry more than one ticket. Manage price, stock, and sales for a ticket in Studio like any other product.

Buying a ticket​

On a ticketed Event, the Attend button becomes Buy ticket with the price. When a ticket is required you'll see "A ticket is required before you can RSVP." If it's optional, a plain Attend sits beside it. A free ticket still goes through checkout. Once you've bought, you're marked Going.

A public ticketed event's own page has a buy button too, so people without a DFOS account can get a ticket. That page is the link to share.

Tickets sell until the event is canceled, deleted, or over. When nothing is left you'll see Sold out. If an event is canceled, tickets already sold still count — holders stay on the list, and nothing is refunded automatically. See Refunds.

If you leave a space, your RSVP goes with you. A bought ticket isn't taken away, and rejoining puts you back on the list. A free ticket an organizer gave you ends when you leave.

The attendee list​

The list of who's going is titled Going · N. On a ticketed event, organizers can also open it from the ticket card. From there, space owners and admins can:

  • Give a ticket — pick a space member to let in free. They're added to the list right away and marked with a Guest badge only organizers see.
  • Remove ticket — take back a free ticket you gave.
  • Export CSV — download the list with email addresses.

Messaging attendees​

Whoever can edit an Event can write to everyone going with Message attendees, on the event's organizer card. Write the message, add a subject, and send. It reaches everyone who RSVPed and can still see the event, by email, except people who've turned email off. You can message attendees of a canceled event too.

  • One message per event per hour.
  • Messages count toward the space's weekly email allowance, the same one email newsletters draw on. The dialog shows how many emails are left.

Events in Studio​

Studio → Reach → Events lists the space's upcoming and past events in one place. Open one to see its attendees, the messages sent, its reminders, and its ticket. The Message history tab shows every attendee message the space has sent.

Canceling and deleting​

Calling an event off and removing it are two different things.

Canceling keeps the event on the calendar, marked canceled, so nobody turns up to something that isn't happening. Everyone who was going is told — by email too, even if they've turned email notifications off, since they said they'd be there. The list of who was coming is kept, and the event can be restored later if plans come back together. A canceled event stops showing publicly.

Deleting takes the event and its attendance list away for good. It's the right move for something made by mistake. If people are already going, cancel instead — the app will offer you that on the way past.

For a repeating event, both apply to the whole series.

Recurring events​

An event can repeat weekly (the same weekday) or monthly (the same day of the month). When you set it to repeat, you also say when it Ends — on a date you pick, or never. Editing a repeating event edits the whole series — a single occurrence can't be moved or rewritten on its own. The one thing an occurrence can carry of its own is its cover image.

Events can be all-day (just leave the time off), carry a cover image and a description, and have a timezone of their own.

Reminders​

The nudges differ by kind:

  • For an Event you're going to — by default you get a push a day before and an hour before, and a ping when it starts. If it's canceled or its time changes, you're told.
  • For an Update — the countdown nudges go to the organizer, until the post is attached. Followers hear when the post actually lands.

Organizers can change an Event's reminders under Event options → Reminders → Customize:

  • Up to 3 reminders, each at 15 minutes, 1 hour, 3 hours, 24 hours, 48 hours, or 1 week before.
  • Push and Email switch on separately for each one. Email is off unless you turn it on.
  • + Message adds a short note to a reminder, up to 200 characters.

The ping at the start is always there. All-day events have no reminders — the row reads "Off for all-day events."

You can follow or unfollow an Update with Follow this update. For an Event, going is what signs you up for its reminders.

Posts on the calendar​

The space's long-form posts show up automatically as small markers on the dates they were made — click one to open the post. Nobody sets this up; it just reflects when the space has been publishing.