What Neo can do with Avanan
- Work an “allowed list request”: add the sender’s address or domain the ticket names to the client’s allow list, after checking the list for an existing entry.
- Block a sender’s address, domain or IP for one client from a “please block this sender” ticket, and remove a block.
- Find a message in Avanan, read Avanan’s verdict and the security event, and quarantine or restore it.
- Manage the exceptions of the anti-malware, DLP, URL reputation, anomaly and click-time protection engines when you allow it.
- Read your client tenants, their licenses and their usage, and create or license a tenant with a technician’s approval.
Your client tenants are mapped to clients
Each Avanan client tenant has a scope, such asmt-prod-3:contoso, whose last part is the tenant’s portal name (contoso.avanan.net). Neo reads the scopes your key reaches, matches each tenant to a client in your PSA, and keeps the mapping on the Avanan card’s Organization Mapping tab, refreshed on each PSA metadata sync. With the mapping, an agent works in the right client’s tenant for each ticket, and on a ticket it can reach that client’s tenant only.
Matching starts with the portal name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC), so the portal contosoltd matches the PSA client “Contoso Ltd”. Last comes an AI match for the long tail.
A name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.
Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right client by hand. A mapping you set by hand survives every later sync.
Next steps
Connect Avanan
Get a Smart API key from Avanan Support and save it in Neo.
