> 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/configuration/platform.md). # Platform The Platform section covers the foundational settings that apply across the entire account. These are the parameters to configure first — before creating passes, connecting systems, or inviting team members.
TitleSummaryCover image
GeneralManage your tenant settings, team members, and core configuration from a single place./pages/g9Fnj5ecOdErumGyeubK/files/ZUoFTnoY83xrJzRzknMC
User AccessInvite team members, assign roles, and control who can view, edit, or manage your platform./pages/dfeWugPHr92B7ziYKsUL/files/DRl7DXdBdiH0akHVZHqe
API KeyGenerate, scope, and revoke API keys for production and staging environments securely./pages/5QqBKqrLt9DepXUvIUWa/files/8Lnp0SGK5xxVBwsFrdvZ
Custom DomainConnect your own domain, configure your CNAME record, and let TWC handle SSL automatically./pages/ZccT0QHtwRjJeb8bnMFZ/files/N9u59v8LiAfwq5vrWcmp
**General settings** define the basic identity of the account: the application title, the favicon displayed on hosted pages, and the languages available for enrolment and pass download pages. These settings are visible to end-users and should reflect the brand's identity from day one. **User access** controls who can log into the back office and with what level of permissions. This is where the administrator account is created, team members are invited, and multi-factor authentication (MFA) is enabled. Keeping access well-defined from the start reduces security risks and avoids confusion when multiple people work on the same account. **API keys** are required for any backend integration. Each key is scoped to the account and must be included in every API request sent to The Wallet Crew. Keys can be created, rotated, and revoked from this section. Anyone setting up a technical integration will need at least one active API key before making their first call. **Custom domain** allows brands to replace The Wallet Crew's default hosted URLs with their own domain — for enrolment forms, pass download pages, and account-linked Wallet journeys. This is a branding decision as much as a technical one: end-users see the brand's domain throughout the experience, not a third-party URL. These four settings are independent of each other and can be configured in any order. That said, completing General settings and User access first is recommended, as they affect how the rest of the platform behaves for the whole team. --- # 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: ``` GET https://docs.thewalletcrew.io/configuration/platform.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.