Email & Remote Approvals
How AIPM reaches you when a sign-off is waiting, and how you can act on it remotely.
Being notified
When an item needs your decision, AIPM can email you. By default the email is notify-only — it simply gives you a generic login link that returns you to your inbox, with no approval id, no evidence text, and no approval details in the message. You sign in and decide inside the authenticated app.
For how items reach you across channels, see Autonomous Orchestration.
Full-mode emails (optional)
An opt-in richer email — chosen by the sender — includes the item’s wording inline, a direct deep link to the specific approval, an Approval-ID, a Content-Hash, and reply-to-approve instructions.
Approving by email reply
When full mode is on, you can reply by email with a decision. Your reply must carry an explicit decision line — DECISION: APPROVE (or DECISION: REJECT) — plus a RATIONALE: line. AIPM verifies the Content-Hash still matches the item and refuses the decision if the item has changed since the email was sent.
The guards that keep it safe
Several checks run before any emailed decision is honored. Every one of them must pass:
- The sender must be on an allowlist.
- The message must pass anti-spoofing checks (DKIM/DMARC).
- It must reference a valid pending approval.
- It must contain an explicit decision line.
- The deciding identity is taken from the allowlist mapping of the sender address, never from the email body.
- Anything that fails a guard is skipped, not acted on.
A human always decides
Email is just a convenient channel — a human always makes the decision. Agents can never grant approvals (rule G-004). For how a decision is recorded against the supporting evidence, see Approving with Evidence.