Skip to main content

Integrations

The Integrations page in the app is where Palisade connects to the systems you already run. There are two kinds of connection, and they do different jobs:

  • A PSA integration keeps Palisade in step with the tool your team works in. Client domains come in from the PSA, tickets go out to it, and billing stays in sync.
  • A DNS connection lets Palisade publish email-authentication records itself, through the account that hosts your DNS, after you approve each change.

If you would rather drive Palisade from your own systems, see Webhooks and the developer portal.

PSA integrations​

Palisade connects to three PSA systems. Each one imports your client domains, opens a ticket in the PSA when the DMARC Agent finds something worth fixing, and keeps domain counts and billing in sync.

note

PSA integrations require an MSP account. If you do not have one, you can upgrade at app.palisade.email/msp-program.

DNS connections​

A DNS connection is a standing authorisation at your DNS provider: Palisade reads the zone, shows you the exact change, and writes it once you approve. One connection sets up every domain in the accounts it can reach, and you can connect more than one account at the same provider.

Palisade connects to Cloudflare and GoDaddy with a scoped API token, and to Amazon Route 53 with a role you create in your own AWS account. Nothing is published without your approval, and the one-time browser flow on each domain's setup page keeps working alongside it.

  • DNS Connections — connecting each provider, choosing zones, statuses, and where publishing happens

Who can do what​

AdminEditorViewer
See integrations and connections, their status and their zonesYesYesYes
Connect a PSA or a DNS provider accountYesYesNo
Rename, re-check, rotate or disconnect a connectionYesYesNo
Choose which zones a DNS connection servesYesYesNo

A viewer reaches the Integrations page and every list on it, and is offered nothing that writes.