Skip to main content
Every event can ask its own questions at registration. A conference needs dietary requirements and an organisation name; a members’ evening needs almost nothing. The form is configured per event, so getting it wrong on one event does not affect the others, and getting it right once does not carry over either.

​
Two kinds of field

System fields are the ones Orgo already knows: name, email, phone, and the rest of the profile. For a logged-in member these arrive already filled in, so the member confirms rather than retypes. Custom fields are yours. They are defined once for your organisation and can then be used on any event form. Available types include short text, long text, number, date, yes/no, single choice, multiple choice, and file upload.
Custom fields belong to the organisation, not to the event. If a field you need does not appear in the picker, it has not been created yet. Create it once in your organisation settings and it becomes available to every event afterwards.

​
Building the form

1

Open the event and go to its registration form

Each event carries its own form configuration.
2

Add the fields you need

Pick from system fields first, since those auto-fill for members. Add custom fields for anything else.
3

Mark the required ones

Any field can be made mandatory. Be deliberate: every required field is a reason for somebody to abandon registration.
4

Test it while logged out

Open the public registration page in a private window. The form a non-member sees is not the form you see as an administrator, and the difference is where problems hide.

​
Collecting more than name and email from public registrations

A public event will otherwise leave you with an email address and nothing else, which is a common regret after the fact. If you intend to follow up with attendees, decide before the event what you need and add those fields, because you cannot ask retrospectively.

​
Troubleshooting

A change to field order does not appear. Reload the public page rather than the editor, and check in a private window. Pages are cached, and you are often looking at the version you loaded before the change. A member is blocked by a question that is not visible. A required field that does not render leaves the member unable to continue with no explanation. This is usually a required custom field that the member’s view cannot display. Make the field optional to unblock them immediately, then report it. You cannot edit the wording of a system field. System field labels are fixed. To ask the question your own way, add a custom field with the wording you want and leave the system field out.