> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Manage Portal Passengers

> Help clients manage their passenger directories in the customer portal, including travel documents and contact details.

This guide covers how portal clients manage their passenger directories and how your operations team interacts with client-submitted passenger data.

<Info>
  **Who should read this:** Operations managers and dispatchers who process passenger data from
  portal clients. Also useful for admins configuring portal passenger settings.

  **Prerequisites:** The customer portal must be enabled with passenger management turned on.
</Info>

## What clients can do

Portal clients have their own passenger directory where they can:

* **Add passengers** -- enter name, contact information, date of birth, and travel documents.
* **Edit passengers** -- update details for existing passengers.
* **Remove passengers** -- delete passengers they no longer need.
* **Assign passengers to trip requests** -- select from their directory when submitting a new trip request.

## Passenger data fields

Clients can provide the following information for each passenger:

| Field                     | Required | Description                                       |
| ------------------------- | :------: | ------------------------------------------------- |
| **Full name**             |    Yes   | First and last name as shown on travel documents. |
| **Email**                 |    No    | Contact email address.                            |
| **Phone**                 |    No    | Contact phone number.                             |
| **Date of birth**         |    No    | Required for international travel (eAPIS).        |
| **Nationality**           |    No    | Country of citizenship.                           |
| **Passport number**       |    No    | Travel document number.                           |
| **Passport expiry**       |    No    | Expiration date of the travel document.           |
| **Known traveler number** |    No    | TSA PreCheck or Global Entry number.              |

<Tip>
  If your operations frequently involve international flights, enable the **Require travel
  documents** setting in portal configuration. This ensures clients provide passport details before
  they can assign passengers to trip requests, reducing back-and-forth before departure.
</Tip>

## How passenger data flows to operations

When a client adds passengers and assigns them to a trip request:

1. Passenger records are created in your workspace's passenger directory, linked to the client's account.
2. When the trip request is accepted and converted to a trip, passengers are automatically added to the trip manifest.
3. Your team can view and verify passenger details on the trip's **Crew and Pax** tab.

## Verify passenger data

After a client submits a trip request with passengers:

<Steps>
  ### Open the trip request

  Navigate to **Operations > Trips > Requests** and click the request.

  ### Review the passenger manifest

  The **Passengers** section shows all passengers the client attached to the request, with their submitted details.

  ### Verify travel documents

  For international trips, confirm that each passenger has valid travel documents:

  * Passport number is present.
  * Passport is not expired and will not expire before the return date.
  * Nationality is recorded for eAPIS filing.

  ### Request missing information

  If any passenger data is incomplete, send a message to the client through the portal messaging system asking them to update the passenger record.
</Steps>

## Edit passenger data from operations

Your operations team can edit passenger records that clients created:

1. Navigate to **Operations > Passengers** and search for the passenger by name.
2. Click the passenger to open their detail page.
3. Edit any fields as needed and save.

<Warning>
  Changes made by your operations team to client-created passengers are reflected in the client's
  portal view. Coordinate with the client before making significant changes to avoid confusion.
</Warning>

## Related

<CardGroup cols={2}>
  <Card title="Manage Passengers" href="/en/how-to/ops/manage-passengers">
    Full passenger management guide for operations staff.
  </Card>

  <Card title="File eAPIS" href="/en/how-to/ops/file-eapis">
    Submit passenger manifests for international flights.
  </Card>

  <Card title="Portal Features Reference" href="/en/reference/portal-features">
    Complete feature list for portal users.
  </Card>
</CardGroup>