> ## Documentation Index
> Fetch the complete documentation index at: https://docs.privy.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
> Understand how Privy authenticates wallet access using user authentication and API authentication.
Privy's wallet system supports granular controls on who can access wallets and what actions different users can perform.
To enforce these controls, Privy's API must verify the identity of the party requesting a wallet action, ensuring that only authorized actions are executed by the system. This process is known as **authentication**.
Privy supports authenticating both **individual** and **organization** users to provision access to wallets.
***
## Individual user authentication
Privy is a powerful toolkit for progressive authentication of individual end users. Fine-grained control over onboarding flows and wallet connections helps improve conversion and craft better UX.
Your app can authenticate users across web2 and web3 accounts, using either an existing authentication provider or Privy's authentication system.
### Using Privy as the authentication provider
If your app doesn't have an existing authentication provider, or needs a single provider for authentication and embedded wallets, your app can use Privy's authentication system, which supports both web2 and web3 accounts.
Privy's client-side SDKs offers a variety of authentication methods, including email, SMS, passkey, socials (Google, Apple, Twitter, Farcaster, etc.), any OAuth system, and Ethereum and Solana wallets.
### Using an existing authentication provider
If your app already has an authentication provider, Privy integrates with your app's [existing authentication system](/authentication/user-authentication/jwt-based-auth/overview). This includes any OIDC compliant authentication system, including OAuth 2.0, Auth0, Firebase, AWS Cognito, and more.
Your app can integrate an existing authentication provider with Privy via the REST API or any of Privy's client-side SDKs.
***
## Organization user authentication
In addition to individuals, a user in Privy may also represent an **organization** of individuals that share authentication and ownership over wallets.
When using an existing authentication provider, your app can configure Privy to authenticate multiple individuals as the same organization user. This enables all individuals within the organization to take action from the wallet, natively integrated with the existing authentication and access control system.
***
## Authentication security levels
Privy's login methods fall into two categories based on their trust model:
### Delegated authentication
A third party controls the credential. Account access depends on that provider remaining available and cooperative.
Examples: Google, Apple, Twitter, Discord, Telegram, email OTP, SMS
### Direct authentication
The user owns the credential outright. No third party can revoke or suspend access.
Examples: passkeys (WebAuthn), hardware keys (YubiKey), TOTP authenticator apps
Account access is wallet access. If your app uses a delegated login method as the primary
authenticator, Privy recommends requiring MFA with either a passkey or authenticator app. [Set up
MFA →](/authentication/user-authentication/mfa/overview) | [Security checklist
→](/security/implementation-guide/security-checklist)
***
## Get started
Authenticate users using just their email address and a one-time passcode.
Authenticate users with their externally owned Ethereum or Solana wallets.
Require passkey or authenticator app MFA to protect delegated logins.
Allow your users to sign into your Farcaster Mini App seamlessly with Privy.