Separate the organizer's account from the guest's reply
The organizer signs in to create, publish, and manage the event. The invited guest opens the public event link, chooses an available slot or replies to the RSVP, and enters a name and email address. Guests do not need an organizer account or a new password.
That distinction belongs in the invitation. A family asked to bring snacks should receive the published event page, not the organizer's dashboard or draft editor. Share through a channel the group already recognizes, such as the school newsletter or club email.
What happens after a guest signs up?
- 1
Open the published event
Read the invitation and choose an available spot.
- 2
Add signup details
Enter a name, email, and any questions the organizer needs. No new account or password.
- 3
Keep the confirmation
The confirmed signup includes a private management link for later changes or cancellation.
Say what the link is asking people to do
A useful invitation answers three things: what help or attendance you need, which date it concerns, and what someone should choose. For example: Please choose one welcome-desk shift for Saturday. You do not need an account; use an email address you can check for your confirmation.
Keep the event description useful on its own. Include the meeting point, timing, and any preparation so the signup still makes sense when someone forwards the link without the original message.
- 1
Publish and open the guest link
Use the share link from the published event. Open it while signed out to check the same page your guests will see.
- 2
Ask for necessary details
Keep name and email, then add only the questions that help you run this event. Explain group counting if one reply may include a family.
- 3
Explain the next step
Tell guests to check their email. If Require email confirmation for signups is on, they must use that confirmation link to complete the reservation.
- 4
Give people a way to make changes
Mention the private management link in their signup email. It is for their own response, not the invitation to forward to friends.
No account does not mean no confirmation step
With email confirmation disabled, a successful signup is confirmed immediately. When the organizer requires confirmation, it starts pending and temporarily holds a place until the guest confirms. If the hold expires, the place is released. Do not describe a pending reservation as finished.
This is different from asking someone to register for the app. It is an email step attached to their event signup. Make that expectation visible before people join a limited-capacity session.
Make cancellations easy to understand
Guests use the management link to review or update their own details and cancel if they can no longer come. A cancellation releases the claimed place. The public event page also offers a way to resend the management email when it has been misplaced.
For individual video appointments, joining details belong with the guest's own confirmed signup. They are not posted as a public list of everybody's meeting links. The meeting section can explain that the organizer has not supplied a link yet.
If a guest still needs help, give them a recognizable way to contact the organizer. Avoid asking them to create an organizer account as a workaround for finding their reservation.
Choose what the next visitor should see
No guest account and public attendee names are separate choices. Review the event's name-visibility settings. The new scenario starters hide public names while still letting visitors see availability; the organizer can review the roster.
Collect sensitive information only when needed, and use the appropriate private question rather than a public description or contribution comment. A friendly low-friction signup should also make it clear what information is being requested and why.
- The shared URL opens the published guest page while signed out.
- The event explains the date, location, and actual commitment.
- Required questions are limited to what the organizer needs.
- Guests know whether an email confirmation is required.
- The management link is described as private.
- Public name visibility matches the group's expectations.