Recall setup
What an operator supplies to connect the Recall Source, and the verification the provider requires.
Connecting Recall 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
Recall refuses the connection until every item holds.
- A Recall account that issues API keys.
- A meeting platform already connected inside Recall, because Recall joins the call rather than Merulan.
Credentials
Recall stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.
- One Recall API key, pasted once and sealed on save.
Scopes
Recall carries no scope list in Merulan: the Recall key itself holds the requested scopes for this Source.
A Recall key carries no scope list, so reach is whatever the Recall account already covers.
Verification
Workspace-issued credential governs the Recall connection. Recall issues the key inside the customer account, so no application review stands between the key and production data.
Related
- 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.