> For the complete documentation index, see [llms.txt](https://community.aidkit.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.aidkit.cloud/apex-your-programs-applicant-and-participant-portal/introducing-apex.md).
# Introducing APEX
For years, AidKit programs have relied on purpose-built links that guide applicants and participants through each step of their journey. While effective, that approach can create confusion over time:
* *"Which link do I need?"*
* *"Did I already complete that survey?"*
* *"Where do I update my information?"*
APEX changes that. APEX gives every applicant and participant a single destination to manage their experience with your program, from application through payment and follow-up activities.
### One destination for every step
Instead of receiving a different link for every action, applicants and participants are directed to a single portal experience. Whether they're starting an application, completing a survey, updating payment information, checking their status, or getting help, they always return to the same place. The result is a simpler experience, fewer dead ends, and greater confidence that participants know exactly where to go next.
### A personalized home base
After signing in, participants land on a personalized Home page that surfaces:
* Open applications
* Required action items
* Upcoming tasks and surveys
* Current program status
* Recommended next steps
Rather than searching through emails for the right link, participants can see everything that needs their attention in one place.
### Built for self-service
APEX helps participants get what they need without contacting support. Standard portal experiences include:
* **Home** for action items and next steps
* **My Profile** for contact information and account details
* **Application Status** for progress tracking
* **Payments** for payment-related activities
* **Help** for support resources and assistance
Participants can update their own information, access program resources, and request help directly from within the portal.
### Configured for your program
While every APEX experience includes a consistent foundation, each portal can be tailored to fit the needs of your program. Working with your AidKit team, you can customize:
* Branding and visual identity
* Page content and messaging
* FAQs and support resources
* Available actions and workflows
* Participant experiences based on program status
The result is a familiar AidKit experience that still feels uniquely yours.
### Why we're excited
APEX represents a shift from a collection of individual interactions to a connected participant experience. Instead of asking people to keep track of links, emails, and next steps, programs can offer a single trusted destination that evolves alongside the participant journey. We believe this will improve completion rates, reduce participant confusion, and create a more intuitive experience for everyone involved.
### Availability
The initial five-page APEX experience is targeted for inclusion in all newly launching AidKit-supported programs beginning in late June 2026.
Interested in bringing APEX to an existing program? Reach out to your AidKit Program Manager to learn more about implementation options.
### Learn More
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://community.aidkit.cloud/apex-your-programs-applicant-and-participant-portal/introducing-apex.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.