How to create a sign-up

A sign-up is the container for one event. Everything else hangs off it: dates (called instances), optional slots, location, capacity, and the public page people use to register. You create the container first, then fill it in.

What you need before you start

You need an account and a team. After you register, open the dashboard and pick the team that should own the event. Sign-ups always belong to a team, even if you are the only member. That is how later teammates can help manage the same roster.

If the event has a physical place, add the location under the team first or create it from the sign-up form. Locations are reused, so “Main Gym” can sit on every basketball date without being retyped.

The create form

From a team, go to Sign-ups and choose Create. The first screen is intentionally short:

• Title (required, up to 200 characters). This is what appears on the public page, search results, and confirmation emails. Use the name people already use: “Spring Concert Volunteers,” not “Event 4.”
• Description (optional, up to 1,000 characters). Put the facts that do not belong in a slot title: who should come, what to bring, parking, or whether kids are welcome.
• Public listing. Off means the event is reachable only by URL. On means it can show up in Search and on the team and creator pages. See Share a public sign-up link.
• Default capacity. A number from 1 to 1,000 that new instances can inherit. You can override it later on a specific date or slot.
• Location. Optional. Pick an existing team location or add a new one.

Saving creates the sign-up and takes you to its management page. At that point there are still no dates, so nobody can register yet.

Add at least one instance

An instance is a date and optional time window. A one-night meeting needs one instance. A six-week class needs six, or a recurrence rule that generates them. Each instance can have its own title, capacity, location, description, and color palette.

If people are choosing a job or an item rather than just showing up, attach slots to the instance or apply a slot template. That difference is covered in Dates versus volunteer slots.

What registrants see

The public page at /signups/{id} shows the title, description, location, upcoming instances, remaining capacity, and the registration form. Organizers who are signed in also get a Manage link back into the team dashboard.

You do not need custom HTML to launch. Layouts and branding exist on some paid plans, but a default page is enough to collect names.

A practical first event

If this is your first sign-up, pick something small: a single meeting with a capacity of 20 and public listing turned off. Share the URL in email or chat. Confirm that a test registration appears on the roster, then delete the test entry. After that, add real dates or slots and turn on public listing only if you want strangers to find it.

Common mistakes: leaving the sign-up with zero instances, setting capacity to 1 by accident, and turning on public listing for a private staff meeting. None of those are fatal. Edit the sign-up or the instance and save again.