# Responses and permissions

Understand publishing access, Pro responses, explicit alarm requests, and revocation.

Choose the least access your workflow needs. Reading public docs, publishing an update, and asking for a response are separate capabilities.

## Public knowledge access

Anyone can read the published docs, pricing, and blog without an account. The public content MCP has read and search tools only. It cannot send alerts, read account activity, or approve actions.

## Publishing access

Publish-only connections can send updates for the connected account. Approve the connection on your iPhone and keep its token in your runtime's secret storage.

Use account sign-in for the [remote MCP](/agent-alerts/docs/remote-mcp), or an iPhone-approved token for the [CLI](/agent-alerts/docs/swift-cli) and [webhook](/agent-alerts/docs/webhook-api). Review the access shown in the connection flow before approving it.

## Interactive responses

Interactive alerts are a Pro feature. They can request a tap, a Yes/No choice, or a text response. Yes/No and text interactions need a notification-capable send; they are not additional Live Activity templates.

A token-based interactive connection requires both publishing and interaction access. It may read responses only for interactions it originated. Keep the returned interaction ID and poll the matching interaction's status through the supported client.

Only an explicit response to that interaction counts as the user's answer. Pending, expired, cancelled, mismatched, or failed responses do not grant permission. A successful send does not mean the user approved the requested action.

## Alarms and scheduling

An alarm requires the user's explicit request and a connection with the required access. Do not turn an ordinary blocker, an unanswered question, or a quiet workflow into an alarm automatically.

Recurring checks belong to your AI client or scheduler. Agree on what to check, how often to refresh, when to escalate, and where a tap should lead before scheduling the work.

## Revoke access

Manage or revoke publisher access in the iPhone app. If a token is lost or exposed, revoke it and create a replacement. Token plaintext cannot be recovered.

Revoking a publisher stops that credential from sending new updates. It does not promise deletion of content already visible on the iPhone. Review [privacy information](/agent-alerts/privacy) before sending sensitive material.


Source: https://www.andreas.ink/agent-alerts/docs/responses-and-permissions
