Para offers extensive customization options to help you create a seamless, branded authentication experience for your users — visual appearance, authentication methods, security features, and third-party integrations. In v3, your partner record is the source of truth for these settings. You manage it in the Para Developer Portal, and the SDK reads it at runtime, so most configuration no longer needs to live in your app code. The Para Modal still accepts props for runtime behavior and per-instance overrides, but the config-related props are now deprecated in favor of the partner record.Documentation Index
Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
Use this file to discover all available pages before exploring further.
How Configuration Works
Developer Portal Customization
The is where you configure the core settings for your Para integration. These settings control technical configuration, email branding, payment providers, and security features.Portal Setup
Email Branding
Payment Integration
Security Settings
Modal Customization
The Para Modal accepts props for runtime behavior (open state, callbacks, default identifier) and per-instance overrides. Note that the config-related props — auth methods, theme, 2FA, guest mode, layout — are now deprecated in favor of the partner record; see How Configuration Works for the supported way to override settings in code (configOverrides).
The is the easiest way to visualize your preferred modal configuration. You can then export the configuration directly into your app.