Skip to main content
Setting up custom terms for your event

Collect Attendees consent with terms on registration form or at event access: A guide to tailoring legal agreements for your event.

Updated over a month ago

Introduction

Custom terms for your event help tailor legal agreements that attendees must accept to access content, interact with others, and participate fully in your event. With Swapcard, you can easily configure these terms to appear at registration or upon event access, providing control over attendee consent and helping meet legal requirements.

How to create and manage Terms

  1. Access the Studio: Navigate to Event Builder and select Terms.

  2. Create Your Terms: Set up the necessary fields, including:

    • Label: An internal name visible only to you for easy reference.

    • Term Description: Detailed text explaining the terms to attendees.

    • Display Location: Choose where the terms will be shown—either on the registration form or when attendees access the event.

  3. Set Terms as Required: Use the toggle option to mark the terms as mandatory if needed.

You can create multiple terms per event and manage them all from the Terms page.

Screen_Shot_2022-08-18_at_16.13.58.png

How do attendees view and accept the terms?

Depending on how you set these up from the Studio, Attendees will either have to accept the Terms through the registration form or when accessing the Event. For the latter, this is how it's going to look like for them:

Screen_Shot_2022-08-18_at_16.22.14.png


Setting up custom terms for your event is a critical step in managing attendee compliance and legal security. By configuring these terms to appear during registration or at event access, you ensure that all participants acknowledge and accept your event’s guidelines. This proactive approach not only enhances your event’s security but also contributes to a smooth and professional attendee experience. Take advantage of Swapcard’s flexible terms management to tailor legal agreements that suit your event’s needs.

Did this answer your question?