Skip to content
Merulan

Affinity setup

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

Connecting Affinity accepts a provider API key the operator pastes once. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Affinity refuses the connection until every item holds.

  • An Affinity account on a plan that issues API keys.
  • An Affinity user whose record visibility covers the lists a Pipeline reads, because the key inherits that user.

Credentials

Affinity stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • One Affinity API key, pasted once and sealed on save.

Scopes

Affinity carries no scope list in Merulan: the Affinity key itself holds the requested scopes for this Source.

An Affinity key carries no scope list. Reach is the issuing user, so narrow the user rather than the key.

Verification

Workspace-issued credential governs the Affinity connection. Affinity issues the key inside the customer account, so no application review stands between the key and production data.

  • 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.