Prerequisites
Before this page: have an embedded wallet (see Post-login user setup) and, if your project uses one, its password.
What you’ll build
Delegated access lets your backend sign for a user’s embedded wallet without a prompt every time — useful for automations, scheduled actions, or server-side flows the user has opted into. You’ll build:
- Status — show whether delegated access is on.
- Grant — turn it on, with the user’s explicit consent.
- Revoke — let the user turn it off at any time.
Showing delegation status
hasDelegatedAccess is a synchronous check for whether the wallet currently has delegated access.
Granting delegated access
Only grant after clear, explicit consent — you’re letting your backend act on the user’s behalf. Pass the wallet password when your project protects wallets with one.
Delegated access means your backend can sign without the user present. Explain exactly what it enables, keep it opt-in, and make revoking easy.
Revoking delegated access
Handling errors
See also