> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/get-started/readme/find-your-starting-point.md).

# Find your starting point

Find the right entry point in The Wallet Crew documentation by role, goal and level of detail, from wallet basics to configuration and developer guides.

Different teams use The Wallet Crew for different reasons. Some need the product model first. Others need data flows, launch sequence, or technical reference. This page points each role to the right first pages.

## Marketing & CRM

Marketing and CRM teams usually arrive asking how the platform works and what it actually does.

The useful first model is simple: design a pass, distribute it, then keep it current after installation. [Understand the platform](https://docs.thewalletcrew.io/get-started/readme/understand-platform.md) gives that lifecycle in one page. [Learn wallet fundamentals](https://docs.thewalletcrew.io/get-started/readme/wallet-fundamentals.md) explains how passes behave in Apple Wallet and Google Wallet. When the goal shifts to acquisition and conversion, [Enrolment](https://docs.thewalletcrew.io/guides-enrolment/) is the right hub for website, email, and in-app entry points.

## IT / Data / Security

IT, data, and security teams usually arrive asking how data is synced and which system owns what.

The main question is usually data flow, not only integration. The Wallet Crew does not store customer personal data by default and links passes to brand systems through identifiers, while core systems stay the source of truth. Start with [Understand the platform](https://docs.thewalletcrew.io/get-started/readme/understand-platform.md), especially the “How it works” section, to place the platform in the stack. Then move to [Pass data and sync](https://docs.thewalletcrew.io/developers-guides/pass-architecture/pass-data-and-sync.md) for identifiers, ownership, and pass architecture, and use [Connectors](https://docs.thewalletcrew.io/connectors/) to review supported integration patterns.

## Developer

Developers usually arrive asking where the technical reference starts and how authentication works.

The shortest route is the [Developers](https://docs.thewalletcrew.io/developers-guides/) area, which groups pass architecture and the webhooks guides. For API key setup, see [API keys & secrets](https://docs.thewalletcrew.io/configure/advanced-configuration/platform/api-keys-and-secrets.md) in Configure. The [API reference](https://docs.thewalletcrew.io/api-reference/) is the next stop for endpoints, payloads, and response shapes. Use [Connectors](https://docs.thewalletcrew.io/connectors/) when the project depends on an existing integration instead of a custom flow.

## Project manager

Project managers usually arrive asking how The Wallet Crew fits into the existing stack and what happens first.

The fastest orientation starts with the [Implementation roadmap](https://docs.thewalletcrew.io/get-started/readme/implementation-roadmap.md), which lays out the common launch sequence from kickoff to go-live. It shows when data ownership, distribution, and operational validation should be decided. [Understand the platform](https://docs.thewalletcrew.io/get-started/readme/understand-platform.md) explains where The Wallet Crew sits between source systems and wallet channels. [Connectors](https://docs.thewalletcrew.io/connectors/) helps map the project against existing CRM, POS, ticketing, and marketing tools.

## Brand admin / operations

Brand admins and operations teams usually arrive asking how to set up the tenant and run it day to day.

Start with [Configure](https://docs.thewalletcrew.io/configure/) for the Apple Wallet and Google Wallet accounts, the custom domain and the settings of your tenant. Then use [Monitoring](https://docs.thewalletcrew.io/guides-monitoring/) to follow passes after issuance and [Scan](https://docs.thewalletcrew.io/guides-scan/) for the in-store or at-the-gate validation.

## Designer

Designers usually arrive asking what a pass can contain and how branding rules apply.

Start with [Learn wallet fundamentals](https://docs.thewalletcrew.io/get-started/readme/wallet-fundamentals.md) for the constraints of each wallet, then go to [Design](https://docs.thewalletcrew.io/guides-design/) for pass types, templates, layouts and assets.

## Stakeholder / Executive

Stakeholders and executives usually arrive asking whether the platform is documented clearly enough to support a decision. Three pages answer that:

* [Understand the platform](https://docs.thewalletcrew.io/get-started/readme/understand-platform.md): the product model, scope and operating principles.
* [Implementation roadmap](https://docs.thewalletcrew.io/get-started/readme/implementation-roadmap.md): the phases and validation points from kickoff to go-live.
* [Policies](https://docs.thewalletcrew.io/policies/): security, privacy and contractual documents.

## Guides by area

To browse by area, see [Browse by topic](https://docs.thewalletcrew.io/get-started/readme.md#browse-by-topic). Most projects start with Configure, then move to Design and Enrolment, so that wallet credentials, domains and provider access are validated before distribution starts. This is the same order as the [Implementation roadmap](https://docs.thewalletcrew.io/get-started/readme/implementation-roadmap.md).


---

# 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://docs.thewalletcrew.io/get-started/readme/find-your-starting-point.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.
