User fields and seasons

You may wish to collect additional information about your users separately of the entry form; for example, their address, title, or occupation. This data is collected through user fields, also known as user resource fields. It is typically information that doesn't change and is associated with their user account rather than with a particular entry. User fields are displayed during registration or when signing in rather than on the entry form.

To learn how to create user fields, check out our guide: Field configuration.

Up until late 2018, user fields were seasonal. This meant for each new season in your program, users would have to complete all user fields again even if those questions didn't change over time. However, you now have the option to make user fields seasonal or non-seasonal. 

Seasonal user fields

Seasonal user fields are season-specific meaning the information you collect from people as they log into your program is only relevant to the active season. When you create a new season, the user fields will be copied over but even if the user had filled the field before, the fields will be blank and will need to be filled again when they log into your program.

Examples of this kind of field could be dates to attend an event or consent to be added to a time based event (like a draw), topics of interest etc

Non-seasonal user fields

Non-seasonal user fields are not specific to any one season meaning the information you collect from people as they register or log into your program will always be associated with their user profile regardless of any new seasons you may have. This can be very handy if you're collecting information that is not likely to change, for example, a contact phone number or address. 

When you create the new user field you'll have the option to make it seasonal in the settings.

Field persists across seasons radio button.png


Was this article helpful?
2 out of 2 found this helpful

Articles in this section