# Approving from your phone

> How to approve send requests from a phone notification, and why your fingerprint is asked first.

- Tool: Warsha Emails
- Section: Safety & recovery
- Applies to version 2026-10-16
- Last updated: 2026-10-16
- Source: https://warshalabs.com

---

## What are you trying to do?

Receive the assistant's send requests on your phone, and approve or reject them from the notification itself — safely, without opening a computer.

> The Android and iPhone apps are **in testing at the moment** and are not yet published in the stores.

## Steps

1. **Install the app and sign in.**

2. **Turn on notifications on this phone** in “Security” → “Notifications on this phone”, and allow them when the phone asks.

3. **When the assistant requests a send** you receive a notification with its details, and two buttons: **“Approve and send”** and **“Reject”**.

4. **On “Approve and send”** the phone asks for **your fingerprint, your face or the device passcode** first; then the request is sent as shown.

## What can go wrong

**“Notifications are blocked for this app.”** Open the phone's Settings → Warsha Emails → Notifications, allow them, and come back.

**“Notifications are not available at the moment.”** Notifications are paused in the service at that moment. Follow requests on the “Approvals” page, which refreshes by itself.

**The notification arrived but the request had expired.** Each request has a time limit set by your plan; ask the assistant for a new one.

## Something you won't expect

**No approval from the lock screen.** Even if you press the button while the phone is locked, nothing is sent before your fingerprint, face or device passcode — so someone holding your locked phone cannot send in your name.

In a browser, the notification only opens the approval page; it never approves from the notification itself.