Skip to content
Merulan

Unipile email setup

What an operator supplies to connect the Unipile email Source, and the verification the provider requires.

Connecting Unipile email is opened by Merulan support on the operator behalf. Merulan support holds the credential. An operator who holds the material below connects in one pass.

Prerequisites

Unipile email refuses the connection until every item holds.

  • A mailbox the aggregator may sign in to.
  • A Merulan support request, because campaign mail pins this Source to the operated path and no direct mailbox connects here.

Credentials

Unipile email stores the credential under the operated custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. Merulan support opens a hosted sign-in session with the vendor, and the resolved handle lands on the connection row.

Scopes

Unipile email carries no scope list in Merulan: the aggregator account that opens the session holds the requested scopes for this Source.

Merulan declares no mailbox scope for this Source, so the reach of the connection is the reach the aggregator negotiated.

Verification

Support-operated connection governs the Unipile email connection. The mail provider admits the aggregator rather than Merulan, so the connection carries the aggregator standing and no Merulan application review.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.