> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.usepassport.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.usepassport.ai/_mcp/server.

# Passport onboard guide

Onboarding to Passport takes two paths. An Admin deploys the Passport Proxy and sets up the APIs your team can access. Each Member then connects their machine and requests access to the APIs they need. Choose your path below.

Passport has the following components:

| Component      | Runs on          | What it does                                             |
| -------------- | ---------------- | -------------------------------------------------------- |
| Passport Proxy | Your environment | Proxies and logs API traffic.                            |
| Passport app   | Passport Cloud   | Enables secret reference issuance and secret resolution. |
| Passport CLI   | Your machine     | Provides the developer-side CLI and daemons.             |

> **Info**
>
> If you aren't ready for a production deployment, you can evaluate Passport first. The [Passport plugin](/passport/reference/passport-plugin/overview/) lets your coding agent [set up a proxy](/passport/reference/passport-plugin/work-with-agent/set-up-a-proxy/), so you can see the end-to-end flow.

## Set up Passport

If you're setting up Passport for your team, see [Set up Passport](/passport/get-started/onboard/admin/). As an Admin, you deploy the Passport Proxy in your environment, register it, and create the namespaces and resources your team can request access to. Your Members connect to this proxy, but they don't deploy anything themselves.

## Start using Passport

If your team already uses Passport, see [Start using Passport](/passport/get-started/onboard/member/). As a Member, you request access to the APIs you need, connect your machine to the proxy using the Passport CLI, and call the APIs with secret references instead of real secrets.