> For the complete documentation index, see [llms.txt](https://docs.pepeunchained.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pepeunchained.com/privy/index.md).

# Privy Configuration Overview

Everything about configuring Privy for a PEPU app: which feature needs which setting, how the SDK and tools verify settings, and where each detail page lives. Start here when login, wallets, sessions or Smart Wallets misbehave.

Menu labels in the dashboard can change; the SDK table `PEPU_PRIVY_REQUIREMENTS` is the checklist of record.

## Prerequisites

* A Privy app. Env: `NEXT_PUBLIC_PRIVY_APP_ID`, `PRIVY_APP_SECRET`.

## Feature to setting matrix

| Feature                                           | Settings it needs                                                                           | Page                                                                  |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Google or email login                             | App ID, secret, Allowed origins (with port), Login methods, Google                          | [Dashboard Settings](/privy/dashboard-settings.md)                    |
| Embedded wallet                                   | Embedded wallets on for Ethereum; server route with the secret; Coinbase `eoaOnly` (code)   | [Embedded Wallets](/onboarding-and-wallets/privy-embedded-wallets.md) |
| Privy session signers                             | Authorization key, key quorum, `PRIVY_AUTHORIZATION_KEY`, `NEXT_PUBLIC_PRIVY_KEY_QUORUM_ID` | [Authorization Keys](/privy/authorization-keys.md)                    |
| Smart Wallets (Privy sponsorship transport)       | Smart Wallets: chain 97741, Kernel, bundler URL, paymaster URL                              | [Dashboard Settings](/privy/dashboard-settings.md)                    |
| Kernel session plus sponsorship (the combination) | Login settings only. No Smart Wallets, no authorization key                                 | [End to End](/onboarding-and-wallets/google-session-sponsored.md)     |

## How settings are verified

* `PEPU_PRIVY_REQUIREMENTS` is one data table: id, where (`dashboard`, `env` or `code`), label, required, pillars, fix and docs URL. It feeds the docs, the MCP tool, the doctor and in-app notices.
* `checkPrivyDashboardConfig` reads the public app-config endpoint and reports pass, fail or unknown for the dashboard rows.
* `pepu_check_privy_config` is that function as an MCP tool.
* `npm run doctor` checks env presence and shape.

Details: [Privy Env Vars and Verification](/privy/env-and-checks.md).

## Pages in this section

* [Privy Setup Walkthrough](/privy/privy-setup.md): the short first-time procedure.
* [Dashboard Settings, Field by Field](/privy/dashboard-settings.md)
* [Authorization Keys and Key Quorums](/privy/authorization-keys.md)
* [Privy Env Vars and Verification](/privy/env-and-checks.md)

## Common failures

| Symptom                                 | Go to                                                                 |
| --------------------------------------- | --------------------------------------------------------------------- |
| Login fails or the iframe is blocked    | Allowed origins in [Dashboard Settings](/privy/dashboard-settings.md) |
| "Creating your wallet..." hangs         | [Embedded Wallets](/onboarding-and-wallets/privy-embedded-wallets.md) |
| 401 "No valid authorization keys"       | [Authorization Keys](/privy/authorization-keys.md)                    |
| "Setting up your smart wallet..." hangs | Smart Wallets in [Dashboard Settings](/privy/dashboard-settings.md)   |

## Related

* [The Three Pillars](/get-started/pillars.md)
* [/privy](/sdk/privy.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.pepeunchained.com/privy/index.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.