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.
What Neo can do with Proofpoint Essentials
Sender Lists
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.
Users
Look up a user’s filtering account, add a new starter or an alias, and deactivate a leaver.
Organizations
Find the client organization behind a ticket and list the organizations under your partner account.
Domains
Check a domain’s mail routing health, verify a new domain, and add DKIM signing.
Organization Settings
Filtering features, external-sender tagging and Azure AD user sync.
Login & SSO
How an organization’s users sign in to the Proofpoint console. Every change waits on a technician.
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
Connect Proofpoint Essentials
Save an admin login in Neo and choose what each agent can do.
