> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/registration-forms/registration-form-user-input.md). # Registration Form - User Input This article explains the different types of user input that can be selected in the registration forms. ### User input The following table describes the various user inputs that you can collect with the 'user input' type: | Name | Description | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | First Name | First name of the user registering | | Infix | Infix of the user registering | | Last Name | Last name of the user registering | | Title | Title of user (Mr., Miss, Mrs., Drs.) | | Email | It is mandatory to fill in the email address, as the email address is necessary for all users on the platform and in the app | | Profile image | Here the users can upload an image as their profile picture. | | Company name | The name of the company that the user is working for | | Company role | Here the user can fill in the role they're fulfilling in the company they're working for. | | Phone number | Here the users can fill in their phone number so other users / connections can reach them | | Description | Here the users can fill in a description | | LinkedIn Profile | Here the users can fill in the URL to the LinkedIn profile. | | Matchmaking tags | Here you can add matchmaking tags for the [matchmaking feature](https://knowledge-base.letsgetdigital.com/the-admin-panel/matchmaking/virtual-platform/match-making). Make sure to create the matchmaking tags already, so that the attendees can pick them while filling out the form. | | Custom | Here you can add ['additional data fields' ](https://knowledge-base.letsgetdigital.com/the-admin-panel/settings/settings/additional-data-fields)of your choice that attendees can fill in. Make sure to first create the 'additional data field', then it will appear here as an option in the form editor. | | User tag select | Users can select user tags pre-defined by you for selection. | #### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/registration-forms/registration-form-user-input.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.