After a user registers for your event, Hubb needs to know what to do with the information they submitted during the registration process. This spreadsheet is where you will capture information such as:
- Where in Hubb should we put the information you have collected?
- Which fields in your registration system correspond to which fields in Hubb?
As you fill out the attached spreadsheet, ask yourself the question: When I look at a Hubb Profile, where do I want to see my registration values appear?
Fields
For each field, enter what you call the field, what your registration provider’s API calls the field, and which Hubb field it should correspond to. Hubb requires mappings for these four fields:
- AttendeeId
- First Name
- Last Name
- Email Address
Other than those required fields, you can add any other fields you’d like to map to Hubb.
Standard Roles
Hubb grants permissions to access different pages and features of the event site based on a user’s roles within Hubb. We need to know which fields in your registration system correspond to these Standard Roles in Hubb:
- Admin
- Attendee
- Expo
- Session Owner
- Speaker
- Speaker Assistant
- Staffer
- Staffing Lead
- Track Owner
One or more of your API fields can correspond to one or more of Hubb’s roles.
NOTE: When the user record comes over the Hubb Standard roles are applied one time. If they are changed in registration after they are brought over the standard roles are not updated in Hubb. This is by design so that standard role changes are always made in Hubb by the event admins.
Custom Roles
We also need to know which fields in your registration system correspond to any Custom Roles you created in Hubb. You will need at least one custom role if you want to use Meetings.