What are the built-in fields in Azavista?
Azavista provides a set of built-in participant fields designed to streamline event management and enhance functionality. Essential fields like email, first name, and last name ensure system reliability, while others, such as preferred language and organization ID, support customization and integration.
This article outlines the available fields, their purposes, and how they enhance participant management within Azavista.
Azavista's built-in fields
Azavista include various natively available fields, including:
- First name
- Last name
- These 3 fields must be used in all forms. They are essential to the functioning of systems relevant to participants.
- Organization ID
- This is the organization of the participant/contact. Organizations are created at Global level -> CRM module -> Organizations
- Preferred language
- Defines which language will the participant see by default (for web pages & emails)
- Profile page ID
- Decides the profile assigned to the contact/participant. It is used for Portals & the Event app, to define the features available to this person.
- Organization manager
- Marks contacts/participants as a manager of their organizations
- CRM status
- Used in relation to CRM integrations, to link the stage/status of the participant in an event to an external CRM
- QR code
- Used for external applications (to create barcodes for example)
- QR codes on badge
- Similar application to QR codes, this field is reserved for badge codes
- Registration time
- Tags the registration time of a participant (i.e. when a form is submitted via a registration workflow)
- Arrival time
- Tags the arrival time of a participant (i.e. when the participant's stage is set to arrived, via the arrival workflow)
- Profile image
- Used to display the image of a participant in the Event app / Check-in app