> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/online-sign-ups/custom-fields-in-sign-up-form.md).

# Collecting Additional Information from Participants at Sign-Up

Need extra information from participants at sign-up — like a health note, national ID number, or kit size? Custom fields let you collect everything your school needs.

## How to add a custom field to a sign-up form

1. Go to *Settings* → *Sign-ups* and click *Edit* next to the form you want to update.
2. Expand the *Client's information* section.
3. Next to *Need another additional field in the form?*, click *Create a new field* and enter its name (for example, ID number).
4. Once saved, find the field in the *Add additional fields to the form* list and click *Add field*.

![Sign-up form editor showing the Client's information section with the Create a new field option](https://2983515171-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL5ksnUuhXGAx5afQd3MB%2Fuploads%2Fgit-blob-5cf81a36189c17c767ee479e299650168793acaf%2FZrzut%20ekranu%202026-05-25%20150617.png?alt=media)


---

# 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://help.activenow.io/en/online-sign-ups/custom-fields-in-sign-up-form.md?ask=<question>&goal=<user_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.