App Access Setup Considerations

There are some things to consider when using an event app at your event. These considerations include app privacy, and how attendees will be accessing the event app. The type of content and event you are running will guide you to best configure your app access.

App Privacy

The privacy of your app, attendee information and App activity depends on the type of event and its attendees. There are three options for app privacy: Private Event, Public Event and Partially Private Event.

Once you’ve determined the best app privacy configuration for your event, how attendees will access the app will become clearer.

Please note

To use any profile-related app features such as the activity feed or in-app badge, attendees must be logged into the app with a profile or registered via the in-app signup form.

Privacy Option 1: Public Access

Public Events are those that have no profile data pre-event and do not need to be hidden from the public. Upon downloading the app, all content and information will be accessible with no login details required. Public access is generally used for events that are open to the public, where attendees can arrive on the day and freely access the event App.

Public Access can be setup with:

No profile login

Considerations:

Does the event app contain content that is private only to registered attendees?

Do I want to track exactly which attendees are using the event app?

Privacy Option 2: Private Access

A Private Access event app is used when the contents of the app should not be shared with the public. The App will be closed off to the public and only accessible using unique profile login information. For additional privacy, content pages can have passwords set to allow for extra security.

A Private Event status can be setup to use unique profile logins. This method can be used to capture attendee login data and force attendees to log into the app before they can access it. This is useful when relying on an in-app badge, or any Attendee Connect features.

Alternatively, a Private Event can be setup with a Shared Password, rather than profile login. This shared password can be distributed among attendees so they can access the app. This is typically used when there are no profiles, but app content cannot be publicly accessible.

Private Access can be setup with:

Profile Login

Shared Password

Shared Password and in-app registration form

Considerations:

Does the event app contain content that is private only to registered attendees?

Do I want to track exactly which attendees are using the event app?

Are any profile-related app features active for this event?

Will the event rely on any profile-related app features (e.g. in-app badge)

Privacy Option 3: Partially Private Access

A Partially Private event app is a Public Access app with some features or pages that are not open to the public.

Partially Private Access can be used when attendee engagement features such as the activity feed or messages are an additional feature, while the rest of the event app is publically available. For example, these features might only be accessible to registered attendees versus those who arrive on the day. When using this option, be aware that profile login is not forced, and login stats will only reflect those who have logged in, not the full list.

Partially Private Access can be setup with:

In-app registration form

Public content with profile login to access features (optional login/signup)

Attendee Connect

In-app badges etc

Considerations:

Does the event app contain content that is private only to registered attendees?

Are any profile-related app features active for this event?

Will the event rely on any profile-related app features (e.g. in-app badge)?

What will encourage attendees to login/register to utilise the profile-related app features?

Attendee Access

App privacy settings need to be configured to match the style of event and attendees. In some instances, the app content will need to be completely hidden from the public (e.g. an exclusive event that only paying attendees can go to), or can be transparent and open (e.g. public tradeshow).

It is important to think about the type of event, its attendees, the data provided and elements being used before choosing an Attendee Access method.

Please note

To use any profile-related app features such as the activity feed or in-app badge, attendees must be logged into the app with a profile or registered via the in-app signup form.

Attendee Access Option 1: Profile Login and Authentication

The most commonly used attendee access method is Profile Login. This option dictates how attendees will log into their personal profile in the event app. Two lines of login credentials (e.g. Username and Password) are required for login, and organisers can control which combination of credentials works best for their event app.

This is the most secure app access method and is recommended when app content is sensitive, private or should only be accessible by registered attendees.

Considerations:

How will you communicate login credentials to all attendees?

What do attendees need to know about accessing the event app?

Attendee Access Option 2: In-app Signup Form

The in-app signup form can be used to allow attendees to register and create their own profiles to access the event app and profile-related features. The in-app signup form allows attendee data to be captured directly into the CMS, allowing for access to an event app that may otherwise be locked to the public.

This access option is not secure at all, as anyone can register themselves through the in-app signup form and access all app content and profile-related app features (e.g. Activity Feed, Profile List etc.)

Considerations:

What profile data do you wish to collect through the in-app signup form?

What do attendees need to know about accessing the event app?

Attendee Access Option 3: Shared Password

Shared passwords are used to keep content private without needing profile data or profile login. This is typically used when there are no profiles or the need for profile-related features (e.g. Activity Feed, Profile List etc.), but event app content cannot be publicly accessible.

This may be a simple way to protect the event app from non-attendees accessing app content, however, it is not a very secure access method. Shared passwords can be easily obtained and anyone can access the event app.