In order to verify the identity of attendees who register for your organization's events, Attendease allows you to assign an authentication method (or a set of authentication methods) to each event. You can choose our built-in authentication method - "Attendease single-sign-on authentication", which is the default - and Facebook authentication. For qualified organizations we also offer custom authentication methods (e.g. via OAuth). 

Authentication is configured for each organization or business unit, allowing for customizability and flexibility depending on the need of each group. You can decide what type of authentication is enabled for each organization or business unit, and whether it is mandatory to use that authentication or not when creating each event. 

Who can configure authentications? Where do they do it?

Authentications are configured on the level of the root organization. This means that only owners of the root organization are able to configure the settings which dictate the authentication methods for the business units and sub-business units below them. 

On the level of the root organization select the Organization tab on the left-hand side and then click the Authentication menu item. On the Authentication screen click to configure your selected authentication method.

Tip: If you are an event author and want to change what type of event authentications are available please contact the owner of the root organization.

How to configure authentications

Determine the availability and configuration of each authentication method for events created in each organization and business unit with the toggles on the Authentication screen. 

Note: Although business units are nested underneath the root organization, the toggle for the root organization does not dictate or affect the settings of any business unit.

"Enabled?" column

Toggle this switch on if you want this authentication method to be enabled for this organization or business unit.

Note: Disabling this toggle for an organization or business unit will affect all live events that are currently using that type of authentication. Since it can negatively affect registration we strongly discourage you from changing the "Enabled?" toggle setting while there are ongoing events. 

"Mandatory for events?" column

This toggle will only be available if you have enabled this authentication method. Toggle this switch on if you want to make it mandatory for all events created in this organization or business unit to use this type of authentication. 

"Default on for events?" column

This toggle will be available only if you have enabled this authentication method and it has been set as optional. Toggle this switch on if you want the checkbox option to be automatically checked when event authors are creating new events (please see section below for more information). 

Note: Editing the toggles in the "Enabled?" column will affect both existing and newly created events, whereas the toggles in the "Mandatory for events?" and "Default on for events?" columns only affect events created after a setting has been changed.

How event authors are affected

Event authors will be affected depending on the authentication configurations made at the root organization level. It may also depend on which business unit an event author is creating an event in, since permissions are set for each organization and business unit individually.

Creating a new event

On the Add Event screen there is a section called "Authentications," in which users will see authentication options if they have been enabled. If an authentication has been enabled there will appear a checkbox option that appears. If it is set as mandatory the checkbox will be greyed out and the event author is unable to edit it. 

If there are no authentications set for that organization or business unit then the "Authentication" section does not appear on this screen.

Note: Authentication on event level is set upon event creation. It cannot be edited after the event has been created. 

On an event

Once an event has been created its authentication method cannot be changed. However, event authors can view what type of authentication is available for that event by clicking the Authentications menu item from the Event tab. 

Note: The exception to this is if the authentication method is disabled for that organization or business unit. Since it can negatively affect registration we strongly discourage you from changing the "Enabled?" toggle setting while there are ongoing events.

How attendees are affected

The registration page will vary slightly depending on what type(s) of authentication method(s) you have enabled. If there are no authentication methods enabled the attendee will be brought directly to the registration form. 

Events that have been set up to use only our built-in authentication, "Attendease single-sign-on authentication," will also direct attendees immediately to the registration form. However, with this enabled the attendee has the option to either sign into an existing account or create a new account by entering their email address and a password.

Note: If there is more than one event pass the attendee will, in both of above scenarios, be asked to select a pass before they are directed to the registration form.

For all events that have Facebook enabled as an authentication method - whether that is the only authentication method or together with our built-in authentication - the attendee must sign in before they are directed to the registration form or event passes page.

On events where both these authentication methods are enabled attendees can either sign in with an existing account, create a new account, or sign in through their Facebook account. 

Did this answer your question?