AIREITERA long email thread can already contain the brief, source files, deadlines, and prior decisions. Perplexity Computer email delegation lets an eligible user turn that thread into a Computer task, but it is best treated as a bounded task trigger, not autonomous inbox management. The key limitation is easy to miss: Computer inherits the verified sender's existing connectors, permissions, settings, and Memory, while its email reply goes only to that sender. Perplexity documents both behaviors in its Help Center.
How Perplexity Computer email delegation works
Perplexity Computer in Email is an alternate entry point to a normal Computer session. Send a new message, forward an existing thread, or add [email protected] to a conversation; Computer reads the supplied context, starts a session, and returns the result in the same thread. It does not create a separate email-only agent with separate permissions. (Perplexity Help Center)
| Stage | What happens | What to verify |
|---|---|---|
| Trigger | A message is sent or forwarded to [email protected], or that address is added to a thread | The sender address matches the Perplexity account |
| Authentication | Perplexity checks the sender and eligibility before creating a task | The account has Computer access; Enterprise access is admin-enabled |
| Context | Computer processes the subject, body, quoted or forwarded text, attachments, and threading metadata | Remove material the task does not need |
| Execution | The task uses the sender's existing connectors, permissions, settings, and Memory | Review connector access before sending |
| Acknowledgment | Computer replies first with confirmation and a link to the session | Open the session to inspect progress and steps |
| Delivery | Computer sends a second reply with the result and any generated files | The reply reaches only the verified sender |
Perplexity says generated artifacts can include PDFs, spreadsheets, images, and videos. Every email-triggered task also appears in the user's regular Computer view on web or mobile, where the session can be continued. (Perplexity Help Center)
Set up the first email-triggered task
Setup requires no add-in, mail rule, or new connector configuration. The three prerequisites are a Perplexity plan with Computer access, use of the same email address associated with the Perplexity account, and administrator enablement for an Enterprise account. Perplexity's page does not name every eligible plan, so the reliable check is whether Computer is available in the account before sending a task. (Perplexity Help Center)
- Open Computer on the web or mobile and confirm the intended connectors and permissions are already configured.
- From the email address used for Perplexity sign-in, compose a message to
[email protected]. The.aiversion of the address is not supported. - Put the instruction in the new message's subject or body. For an existing conversation, forward the thread and place the instruction above the forwarded material, or add Computer to the thread.
- Name each attachment in the instruction and specify the required output, such as a cleaned spreadsheet or a PDF summary.
- Wait for the acknowledgment, then use its Perplexity link to inspect the Computer session. A later message in the same thread carries the completed result.
- Reply in that thread to request a revision; Computer retains the task context for the follow-up. (Perplexity Help Center)
A useful request separates the authorized instruction from source material:
Task: Summarize the decisions and unresolved questions in this thread.
Output: Return a two-column spreadsheet with owner and due date.
Constraints: Use only dates and names present in the thread. Mark missing fields
as "Needs verification." Do not send messages or update connected systems.
Attachments: Use project-status.csv as supporting context.That format is not required by Perplexity, but explicit output and action constraints reduce ambiguity. The official example similarly asks Computer to clean an attached CSV, remove duplicates, and return a formatted spreadsheet. (Perplexity Help Center)
What is auditable after an email task
Each email request creates a standard Computer session, so auditability is stronger than an opaque email-only response. The acknowledgment links to the session, and Perplexity says users can review its task steps on web or mobile; administrators in eligible organizations can also view Computer activity through Audit Logs. (Perplexity Help Center)
The documented evidence has limits. Perplexity does not specify on the public help page whether the session exposes every connector read, attempted action, credit charge, or failure in an exportable event log. A visible sequence of task steps therefore supports review, but it should not be described as a complete forensic record unless an organization's Audit Logs prove that for its own configuration.
For a reviewable workflow, retain the original request, inspect the linked session before using the deliverable, and record human approval outside Perplexity when the result affects a customer, payment, contract, or production system. The first two controls map directly to the documented thread and session behavior; the approval record is an operating control, not a Perplexity feature.
Permission and privacy boundaries before forwarding
Computer acts as the verified sender, not as every participant in the thread. It uses that user's existing connector permissions and Memory, so forwarding an email does not grant new access, but it can invoke access that was already configured. (Perplexity Help Center)
Perplexity draws an important instruction boundary: the verified sender's subject and body are treated as the request, while quoted messages, forwarded third-party text, and attachments are context rather than trusted instructions that can override the sender, system rules, or safety policy. That design reduces prompt-injection authority; it does not establish that every output will be accurate or unaffected by malicious context. (Perplexity Help Center)
The service may process sender and recipient headers, subject and body text, quoted and forwarded context, attachments, message IDs and references, thread and delivery metadata, generated replies, generated attachments, and Computer task/session metadata. Perplexity states that the data is encrypted in transit and at rest on SOC 2 Type II-certified infrastructure, and that email messages, attachments, and enterprise data are not used for model training. It also says human access follows its standard authorized processes for production, support, security, legal, and compliance. (Perplexity Help Center)
Before forwarding, remove unrelated recipients' personal data, old attachments, hidden quoted history, contract language, credentials, and signatures that are not necessary for the task. Convenience removes the manual copy-and-paste step that often doubles as a redaction checkpoint.
That concern is not theoretical for users deciding whether to connect inbox workflows. In a discussion about Perplexity's email products, Reddit user u/followspace wrote:
“I don't want to use yet another service that has access to my inbox.” Source: u/followspace on r/perplexity_ai
Computer in Email does not require granting a new mailbox-wide connector merely to send a task, according to the setup documentation. However, any connectors already available to Computer remain relevant, and the emailed thread and attachments are still processed by Perplexity.
Operational limits that change the recommendation
The current workflow is asynchronous, sender-bound, and dependent on existing account access. Several practical limits are documented; other limits remain undisclosed on the public Help Center page. (Perplexity Help Center)
| Limit or behavior | Documented status | Operational consequence |
|---|---|---|
| Reply audience | Only the verified sender receives Computer's reply; this is not configurable | CC does not create a shared agent participant or Reply All workflow |
| Sender identity | Must map to an eligible Perplexity user with Computer access | Aliases or alternate addresses may fail if they do not match the account |
| Message screening | BCC-only, auto-generated, bulk, list, bounce, and loop mail are rejected | Mail rules and automated notification pipelines are not dependable triggers |
| Permissions | Existing Computer connectors and permissions carry over | Review access before delegating, especially write-capable connectors |
| Attachment formats and size | No complete public limit is stated | Test representative files before adopting the workflow |
| Task latency and concurrency | No service guarantee is stated | Do not use it for deadline-critical or real-time operations |
| Task or credit allowance | No email-specific quota is stated | Check account usage rather than assuming email tasks are unlimited |
| Retention duration | The page references the same retention controls as Computer but gives no duration | Apply the organization's configured policy and verify it with an administrator |
| Continuous monitoring | Not described as a mailbox watcher or scheduler | Treat each accepted email as a discrete trigger |
Community questions reinforce the need to verify entitlement instead of inferring it from marketing language. One Reddit user asking about a recurring digest was told that such work could consume substantial Computer credits; because this is user discussion rather than official pricing documentation, it is a reason to inspect account limits, not evidence of a fixed cost. (Reddit thread)
Decide what to delegate
Perplexity Computer email delegation is a good fit when the input is already in a thread, the output can be reviewed before use, and the task can run under existing permissions. It is a poor fit when a mistaken action would create an external commitment or when the thread contains more sensitive data than the task requires.
| Delegation class | Examples | Required control |
|---|---|---|
| Good first tasks | Summarize a thread; extract open questions; clean a non-sensitive CSV; create an internal draft | Inspect the session and compare output with source material |
| Delegate with approval | Draft a customer response; prepare a financial model; analyze contract text; transform internal records | Human checks facts, numbers, recipients, permissions, and final file before use |
| Keep human-controlled | Send binding commitments; approve payments; accept contract terms; delete records; handle secrets or regulated data without an approved policy | Do not rely on an email-triggered task as the authorization mechanism |
The recommendation is unambiguous: use Computer in Email for reversible preparation and document work first. Keep sending, approval, deletion, and binding decisions behind a separate human checkpoint, even when a connected tool technically permits those actions.
FAQ
What is the correct Perplexity Computer email address?
Use [email protected]. Perplexity explicitly says [email protected] is unsupported. (Perplexity Help Center)
Can Perplexity Computer read attachments sent by email?
Yes. Perplexity says Computer can use attached files as context and return generated PDFs, spreadsheets, images, videos, and other artifacts as attachments. The public page does not publish a complete file-type or size limit. (Perplexity Help Center)
Does everyone in a CC'd thread receive the result?
No. Computer currently replies only to the verified sender, even when other people are on the thread, and that behavior is not configurable. Share the underlying Computer session separately when appropriate. (Perplexity Help Center)
What happens if I send from another email address?
The sender must map to the existing Perplexity account and have Computer access. Use the same address used to sign in; otherwise the system cannot associate the request with the user's settings and permissions. (Perplexity Help Center)
Is Computer in Email the same as connecting Perplexity to my whole inbox?
No. Sending or forwarding a message is a discrete task trigger, and the setup page says nothing needs to be installed or configured. The task still processes the supplied thread and files and can use connectors already configured in Computer, so both the forwarded content and existing permissions require review. (Perplexity Help Center)
Are emailed messages and attachments used for model training?
Perplexity states that email messages, attachments, and enterprise data used by Computer in Email are not used for model training. Organizations should separately confirm retention, residency, and connector policies required by their own compliance program. (Perplexity Help Center)