Overview
FaceSign provides customization options for the permissions page shown before verification begins and global UI control settings. Customizations are applied when creating a session.Customizations are optional. If not provided, FaceSign uses sensible defaults with your configured avatar.
Permissions Page
ThepermissionsPage property customizes the page that asks for camera/microphone permissions. Use it to change text, background, and translations.
Available Options
Permissions Page Customization
UI Controls
Global UI control settings that apply throughout the verification session.Available Options
UI Controls Customization
Multi-language Support
Use Translates fields to provide translated text for multi-language sessions. Language keys should match ISO codes.Translation Fields
Multi-language sessions also require
langs and defaultLang fields at the session level.Multi-language Example
Implementation
Supply acustomization object when creating a session. Nested fields are optional — only include what’s needed.
Complete Example
This example shows all customization options combined: custom permissions page with color background, multi-language support for English/Spanish/French, and hidden UX controls for a minimal interface.- cURL
- JavaScript
- Python
Common Examples
Minimal Branding
Customize just the heading and button text:Minimal Setup
Avatar Background
Default (avatar video):Avatar Background
Color Background
Solid color (with heading and subheading):Color Background
Multi-language
Switchable “en”/“es”:Bilingual Setup
Test your customizations across different devices and screen sizes to ensure a consistent user experience.
Auto-brand from your website (FaceSign MCP)
Thecustomization fields above cover the FaceSign-hosted permissions page. If you want the same brand applied to the landing and recap pages that wrap the session in your own app — typically generated through the FaceSign MCP server with launch_session_ui or export_app — you can point the AI agent at your product website and have it pull the visual language automatically.
Hand the agent a reference URL and ask for a branded demo, for example:
“Use https://acme.example.com as the style reference.”
The agent fetches the page with its own web-fetch tool, reads the HTML and CSS, and adopts:
- Primary accent color — scanned from CSS custom properties (
--primary,--brand,--accent) and the most frequent hex on buttons and links. - Typography — the first two
font-familydeclarations onbodyand headings. - Border-radius scale — taken from buttons and cards.
- Shadow style — subtle vs. strong drop-shadow feel.
- Logo — the first
<img>inside<header>(or withaltmatching the brand name).
Next steps
Sessions
Create sessions with customization
Languages
Multi-language support
Avatars
Choose AI avatars