Review the operation and its limit before connecting a service. Connections are enabled per organization from inside the application.
Organization consent, object and field scopes, and the responsible CRM identity must match the task. Read, write and sync permissions are separate. No connection is established by this page.
Only an explicitly approved operation may run. Tool discovery is not execution authority. Read access, write access, usage controls and human review each retain their own limits.
Public sources, customer-authorized imports and licensed data have different permissions. Provider names do not establish access to every dataset. Preserve retrieval dates and source-specific limits.
Hosted credentials, allowed tenants and callback destinations require confirmation. Enablement is confirmed per organization.
No hosted provider is activated here. Existing-account linking needs independent ownership proof.
An active organization membership and its SSO policy are both required. Native callback allowlists need verification.
Supported source handlers must be verified per tenant. A directory update does not grant candidate or personal-record ownership.
Native signature and portal acknowledgment remain distinct. Provider upload, callbacks and protected downloads need authoritative receipts.