> 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/client-management/cannot-find-participant.md). # Can't Find a Participant in the List If a participant isn't showing up in search results in the *Participants* tab, check two things: ## Check which columns are visible Search only works on columns that are visible in the table. If you're looking for a participant by phone number or email address, make sure those columns are enabled — in the *Participants* tab, click *Change columns* and tick *Phone number* or *Email*. Once saved, you'll be able to search by those fields. ## Check the inactive participants tab By default, the participant list only shows **active** participants — those who are currently attending courses. If a participant isn't currently attending any courses, the system moves them automatically to the inactive list. To find them, click the ***Active*** button in the top-left corner of the *Participants* tab and select ***Inactive*** from the dropdown menu. --- # 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/client-management/cannot-find-participant.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.