THIS ARTICLE HAS BEEN ARCHIVED AS OF SEPTEMBER 2019. THE INFORMATION CONTAINED WITHIN MAY NOT BE CURRENT. PLEASE CONTACT ENTEGY SUPPORT IF YOU REQUIRE ASSISTANCE.
Attendee: Someone attending the event and using the event app (e.g. speaker, sponsor, attendee etc.).
Profile Type: Used to segment profiles into distinct groups such as attendee, speaker etc.
Profile Field: Refers to all profile information in the Core (CMS). There are three types of profile fields: Fixed Fields, Identification Fields and Customisable Fields.
Fixed Field: Profile fields already set up by default in the Core (CMS) (e.g. First Name, Last Name, Organisation etc.)
Identification Field: Used for profile identification in the Core (CMS). Attendees can also use these when logging into the event app.
Customisable Field: Created for additional information or to enhance element functionality (e.g. gala dinner ticket, postcode, years of service or alternate contact number).
Custom Multiple Choice Field: Created for additional profile information that has more than one possible answer. Multiple choice fields are the most versatile when working with elements in the system, and increase flexibility with personalisation and data collection.
Custom Text Field: Store the text that has been input that can then be placed throughout the app (e.g. on an attendee’s profile in the profile list). Each project is limited to 10 text fields.
Organiser permissions: Profile types with organiser permissions allow for extra functionality in the app, such as deleting comments from the Activity Feed.
Snapshot: Creates a backup of profile data to be saved and later restored if required. Snapshots can be used to reverse undesired changes made to profiles and/or profile types.
External Reference: A unique string of characters (not limited to numbers) that are populated by an event organiser when profiles are imported (e.g. membership ID, registration number, ticket number etc). This can be used to log into the event app.
Internal Reference: A unique string of numbers that are generated by the Core (CMS) for each attendee. These are automatically determined when a profile is created and cannot be changed.
Authentication: How attendees will be verified when accessing the app (e.g. login methods, download details etc.).
Username: A combination of First Name, Last Name and 4 characters e.g. John.Smith5487. Attendees can personalise this username once they have logged in, through their account settings.
Password: A temporary password auto-generated by the Core. Attendees can then update their password on first login in, meeting the required complexity selected by the organiser.
Email (login option): Email addresses must be unique for all attendees if used as a login method. This cannot be used if you have allowed duplicate emails in Profile Field settings.
Visible in list/Visible to others in the app: The attendee’s name and visible profile information will appear in the profile list.
Allow Messaging: An attendee can be messaged by another attendee.
Connections: Personal attendee and exhibitor scans. When set to Connections, this will always display/share an attendee’s email address or contact number with their connection.