> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What the Proofpoint Essentials integration brings to your Neo Agent setup

Proofpoint Essentials filters email for your clients. The most common ticket it causes is "an email I need was held, please let it through". Connect Proofpoint Essentials to Neo and your agents can find the client's organization, add the sender to the right safe list, and manage users and domains from the ticket. Nobody opens the Proofpoint console for the allow-list part of the job.

<Warning>
  Proofpoint's published Essentials API document has no quarantine endpoint. Neo can stop the sender's **next** email from being held, but it cannot release a message that is already in quarantine. The user releases it from their quarantine digest email, or a technician releases it in the Proofpoint Essentials console. The agent says this on the ticket.
</Warning>

<Info>
  Proofpoint Essentials uses one admin login per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent.
</Info>

## What Neo can do with Proofpoint Essentials

<CardGroup cols={2}>
  <Card title="Sender Lists" icon="list-check">
    Add a sender, a domain or an IP address to a client's safe list or block list, for the whole organization or for one user.
  </Card>

  <Card title="Users" icon="users">
    Look up a user's filtering account, add a new starter or an alias, and deactivate a leaver.
  </Card>

  <Card title="Organizations" icon="building">
    Find the client organization behind a ticket and list the organizations under your partner account.
  </Card>

  <Card title="Domains" icon="globe">
    Check a domain's mail routing health, verify a new domain, and add DKIM signing.
  </Card>

  <Card title="Organization Settings" icon="sliders">
    Filtering features, external-sender tagging and Azure AD user sync.
  </Card>

  <Card title="Login & SSO" icon="key">
    How an organization's users sign in to the Proofpoint console. Every change waits on a technician.
  </Card>
</CardGroup>

Licensing & Products and Reporting & Billing are also available, read only: licence counts for renewals, and mail flow statistics for QBRs.

## Your clients are mapped automatically

Neo matches your Proofpoint Essentials customer organizations to the companies in your PSA and keeps the mapping on the Proofpoint Essentials card's **Organization Mapping** tab, refreshed on each PSA metadata sync. Your own partner organization is not a client, so it is not mapped.

Matching is by name first: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Then by domain: an organization's mail domains against the website on each PSA company. Last comes an AI match for the long tail.

**A name match, or one you confirm, is handed straight to your agents**, so they know the client's Proofpoint organization without looking it up. A domain match or an AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it, and an agent that looks the company up can still find it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

## Next steps

<Card title="Connect Proofpoint Essentials" icon="plug" href="/integrations/proofpoint-essentials/connecting-to-neo">
  Save an admin login in Neo and choose what each agent can do.
</Card>