Unique Emails

Tip:

When containers are not being used, it is still possible to force users to use unique email addresses using the following setting:

• Only allow unique emails

Unique emails in Subscription Containers

When a subscription container is used, one environment acts as the master, and all linked events become child environments.

If the Container master mode is set to Unique emails, this rule applies to all child environments linked to that container.

This is required to support cross-event access within a container.

Environment is set to act master (container) with the unique emails mode.

What does “Unique emails” mean?

When Unique emails is enabled:

• A single email address can be used to register for multiple child environments

• Users can log in once and switch between events they are registered for

• The system can reliably recognise and verify returning users across events

When should you use Unique Emails?

Unique emails are recommended when:

• You run multiple related events

• Attendees regularly attend more than one event

• You want users to switch between events without creating new accounts

• You need stronger protection against account misuse

List of linked events in app

How the system works

• User identity data is stored centrally at the container (master) level

• When a user registers for a new child environment:

  • The system checks whether the email address already exists within the container

  • If the email does not yet exist:

    • A new user is created as part of a standard registration flow

    • The user record is added to the container and linked to the child environment

  • If the email already exists:

    • The user is required to verify their identity via email

    • After successful verification, a new user record is created in the child environment

    • If the verification code is not used, the user is not created

• The user can then:

  • Log in using the same credentials

  • Switch between all events where their email address is registered

This approach provides both convenience for returning attendees and security against unauthorised access.

User must enter verification code when registering with existing email.

Imported users and external systems

When users are imported from external sources (for example ticketing partners like Weeztix or tools like HubSpot):

• Multiple users may share the same email address

• To keep users distinguishable, the system automatically makes email addresses unique

  • Example: [email protected]

• All emails are still delivered to the same inbox

These users can later be corrected by:

• Editing the email address in the Admin Panel, or

• Reassigning tickets to the correct attendee