Troubleshooting and access

Access and your data

Understand sign-in, email account connections, agent identities and grants, and what disconnecting or deleting removes.

When to use it

Use this guide before granting access or removing a connection, so you know which permission belongs to Doorbell and which belongs to your agent.

Example

You sign in with Google but monitor an Outlook account. Your Doorbell sign-in, Outlook connection, and the invoice agent’s own email access are three separate authorizations.

Set it up

  1. Sign in with the exact invited address using an emailed six-digit code, a password you set, or Google sign-in when offered. A +alias needs its own invitation.
  2. To set or replace a password, open your email address or Account in the header. If you forget it, sign in with an emailed code first.
  3. Authorize each provider under Integrations > Sources. For Teams, verify your Microsoft identity and link the installation separately. On MCP consent, choose the agent identity, capabilities, and mailbox choice. Deny requests you did not start.
  4. In Mailboxes, select a mailbox and open Configure > Agent access to grant only needed mailboxes. Approve Organize mail separately when shared changes are needed. Capture choices apply to every mailbox the source feeds. Keep destination URLs and keys in secure fields.
  5. Before disconnecting a source or permanently removing mail, review the scope and impact. Use Mail for recoverable Trash and scoped permanent removal. To delete all customer data, open Account and confirm Delete my customer data with your sign-in address.

Important limits

  • Google sign-in does not grant Gmail monitoring. Doorbell's email account connection does not grant your agent email access. Teams identity verification does not grant email access.
  • Doorbell does not fetch email bodies, previews, or attachments. It retains identity and approved metadata. Webhooks retain declared scalars and approved bounded JSON, not raw requests. MCP text is not a document upload.
  • Teams may capture addressed text and attachment descriptors, not files. Only the linked sender's routes admit those messages. Slack captures selected new messages under the connected human's policy. Text is optional and group DMs require opt-in.
  • New connections default to Messaging only within the signed request. Setup/admin and Organize shared mail require separate approval. Narrowing retires that connection's older credentials; later expansion does not revive them. Other connections remain independent.
  • An agent sees only granted mailboxes; an ungranted mailbox looks missing. A connection capability and a mailbox grant must both allow an action. Read uses notifiers:read, sending uses messages:publish, and organization needs both mail:organize and per-mailbox Organize mail permission.
  • Configuration, credentials, destructive actions, and provider management use separate capabilities. Source messages and claimed approval fields cannot authorize configuration changes or expand task authority.
  • Removing a grant, send permission, or agent takes effect on the next request. Accepted mail stays. Source revocation blocks capture and reads. A pending reference-only notice may still deliver if it also covers other available mail. Reconnect does not restore revoked content or import missed activity.
  • Archive and Trash are shared organization, not deletion or permanent storage. Restore and Undo respect source access and the original seven-day acceptance expiry. Neither changes read state or external originals.
  • Permanent removal hides every received and Sent role in one mailbox, including labels, search, and conversations. It leaves other mailboxes unchanged. Content erasure scrubs the selected content and derived copies throughout Doorbell. Both require the customer or an explicitly authorized admin and scoped confirmation. Ordinary Messaging and Organize cannot perform them.
  • Restore, Undo, silent backfill, and an original-send retry cannot recreate permanently removed membership. Content-free receipts can remain. Neither removal nor erasure changes external originals or recalls data already retrieved or transmitted, or requests in flight.
  • Deleting a mailbox removes its routes, triggers, grants, and memberships, not other mailboxes' messages or shared destinations. Customer data deletion ends sessions and connections and removes live customer data. External workflows and backups until expiry remain outside that operation. An invitation can remain, so deletion alone does not revoke pilot access.

Troubleshooting

  • If a sign-in code expires, request a new one and use the latest email. Codes expire after ten minutes and work once.
  • If you cannot sign in, check the exact invitation address or request pilot access. For deletion after access has ended, contact privacy@agentdoorbell.com.
  • If email or agent access is refused, check that authorization separately rather than reconnecting an unrelated sign-in. If an agent cannot see a mailbox, check its grants.
Technical reference

Messages expire seven days after acceptance, including unread, archived, and trashed mail. Customer-private drafts expire seven days after first save. Reading, edits, organizing, restoring, and delivery do not extend those lifetimes. Delivery history and send retry guarantees are bounded to seven days too.

preview_mail_removal takes mailboxId, explicit messageId and revision selection, and scope mailbox or content. After customer approval, confirm_mail_removal repeats that exact scope and selection with the returned confirmation. Agent calls need a mailbox grant plus configuration:write and configuration:destructive; changed scope or revisions need a new preview.

Gmail requests metadata-only access. Outlook requests basic mail access and may fall back to Mail.Read if basic access is not granted; Doorbell still requests only metadata. The privacy policy records legal disclosures and retention details.

For legal disclosures, read the privacy policy.

Open Agent Doorbell