01Unified operation verification requiredCRM record context · Salesforce and HubSpot
Read permitted records; separately review write scope
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.
Prepare a question02Approved manifest and scoped identity requiredApproved tool access
Supervised tools for a defined workflow
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.
Prepare a question03Dataset, coverage and freshness verification requiredIntelligence and customer-connected data
Read entitled notices, award history and imported context
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.
Prepare a question04Availability not verifiedGoogle sign-in
Primary account sign-in and callback
Hosted credentials, allowed tenants and callback destinations require confirmation. Enablement is confirmed per organization.
Prepare a question05Availability not verifiedMicrosoft sign-in
Primary account sign-in and callback
No hosted provider is activated here. Existing-account linking needs independent ownership proof.
Prepare a question06Organization-specific configuration requiredOrganization SSO
Organization authentication restriction
An active organization membership and its SSO policy are both required. Native callback allowlists need verification.
Prepare a question07Source capability; unified connection unverifiedDirectory provisioning
Existing SCIM and lifecycle operations
Supported source handlers must be verified per tenant. A directory update does not grant candidate or personal-record ownership.
Prepare a question08Source operations; adapter verification requiredDocument and signature services
Original document storage, signing and protected export
Native signature and portal acknowledgment remain distinct. Provider upload, callbacks and protected downloads need authoritative receipts.
Prepare a question Keep the boundary clearNo provider is activated, linked or given access by this preview. Read, write, synchronization and identity permissions must be reviewed separately.