Event details

• Confirm event name, date, time, venue name, location, and maps link.
• Check that the event status allows the host to edit if they need to complete planning.

Planning visibility

• Open the timeline and confirm the correct cards are visible to hosts.
• Lock any cards the host should not edit.
• Make sure notes and questions only appear where they are supposed to.

Links and features

• Copy the generated host link from the event.
• Turn guest requests on or off according to the event workflow.
• Confirm documents, photos, photobooth, or music features only appear when they are meant to be used.

Related articles

Why this matters

• A client or planner with multiple events should not need a separate login for every event.
• One account makes it easier to manage repeat bookings and reduces support issues.

Recommended workflow

• Search for or create the host user first.
• Assign the host to each event they should access.
• Send one magic link so they can create or open their account and see the assigned events.

Guest links are different

• Guest links are event-specific and should be used for limited guest participation such as song requests or photo access.
• Hosts should use host access when they need planning permissions.

Related articles

Host links

• Use the host link for the client, couple, planner, or event owner who should help complete planning details.
• Repeat hosts should be assigned to multiple events under one account instead of receiving separate logins for every event.

Guest links

• Use the guest link for guest-facing requests such as song requests or event photo galleries when those features are enabled.
• Turning guest requests off should not erase data already collected.

Security note

• Only share links with the people who should access that event. If a link is exposed publicly by mistake, contact the workspace admin so access can be reset or locked down.

Related articles