If users want to sync their schedule and notes across devices, participate in chat, post photos in the activity feed, etc., they will need to be logged in. The EventPilot platform offers a variety of login integration options.
Which authentications options are available?
Default: Account creation including Social Media Logins
If you do not have any means to link login with your registration membership system, your attendees can simply create an account within the platform directly. Using this option, they can also quickly log in using a social media option such as Google or LinkedIn login.
Authentication via Attendee List
If you have the ability to create an attendee as a spreadsheet, you can use it to set up authentication. Define one column in the spreadsheet as their username (this could be a number you assign or their email). Usernames must be unique. The password is automatically the user's last name in the spreadsheet.
Authentication Integration with the registration system from CDS
EventPilot Premium and Pro
EventPilot can be set up to integrate with your CDS registration. Attendees then log in using the badge ID as the username and their last name (as they registered) as the password.
Authentication Integration with the registration system from Maritz
EventPilot Premium and Pro
EventPilot can be set up to integrate with your Martiz registration. Attendees then log in using the registration number as the username and their last name (as they registered) as the password.
Custom Authentication Setup
EventPilot Pro only
Your team at ATIV can set up a custom integration for you.
For example, you may be using a Salesforce based Membership system with OAuth so your attendees would use their familiar member login. However, only members that actually registered via your third party registration platform are allowed to log into the platform.
These types of authentications must be set up and fully tested early in the project. Contact your project manager at ATIV.
You can set up the platform to have no authentication at all. This will limit functionality for your users but may be useful if you only want to provide a completely open web program for example.
When are users prompted to log in?
By default, platform users can browse the event program, see the list of exhibitors or speakers, review your general information, view abstracts.
The login prompt only appears as needed to use a certain feature. Examples:
- a web app user must log in to add sessions to their schedule (native app users do not need to log in to add sessions or notes)
- If you display the attendee list, users must login to access it
- Share a photo in the activity feed
- Join a virtual session (if set up via the Virtual Sessions add-on)
- Watch a Simulive session (if add-on is used)
- Access any files uploaded by speakers via the Speaker Portal
- Sync the schedule, notes, bookmarks across devices
- Post in a session chat
- Message another attendee
It is possible to completely restrict all access to the event program where only logged in users can browse the program. In this case, the login prompt appears before the Home Screen loads. Users cannot access the Home Screen, the search, or any of the tabs unless they first log in.