Creating Your Account
Sign up with Google OAuth, complete the onboarding wizard, and configure your first authentication method.
Go to signedapproval.net
Visit signedapproval.net and click Sign In in the top navigation. You'll be redirected to Google's OAuth consent screen.
Sign in with Google
Choose the Google account you want to use as your approver identity. This email address will be associated with all your approval decisions. Choose carefully — this is the identity that callers will associate with your signed approvals.
Complete the onboarding wizard
After your first login, you'll be redirected to the onboarding wizard at /onboarding. The wizard has three steps:
- Welcome — Overview of what SignedApproval does and how it works.
- Authentication Setup — Register at least one authentication method (passkey or TOTP). You need this to approve requests.
- iOS App — Optional: download the iOS app for mobile approvals with push notifications.
Register an authentication method
You must register at least one authentication method before you can approve requests. You have two options:
- Passkey (recommended) — Uses WebAuthn/FIDO2. Works with hardware security keys (YubiKey), platform authenticators (Touch ID, Windows Hello), or passkey managers (iCloud Keychain, 1Password).
- TOTP Authenticator — Scan a QR code with Google Authenticator, Authy, or any TOTP-compatible app.
You can register both methods and choose which to use when approving each request.
Access your dashboard
After completing onboarding, you'll land on your dashboard at /dashboard. From here you can:
- View pending and past approval requests
- Manage your authentication methods
- Create and manage API keys
- Configure preferences like quiet hours and default TTL
- Set up integrations with GitHub, Bitbucket, GitLab, and more
Account Security
Your SignedApproval account is protected by multiple layers:
- Google OAuth — No passwords stored in SignedApproval. Your Google account's MFA protects your login.
- Ed25519 signing keys — Generated automatically on your first approval. Private keys are encrypted with AES-256-GCM.
- Per-approval authentication — Even after logging in, each approval requires re-authentication via passkey, TOTP, or Face ID.