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.
Technical information
Understand the
integration boundary.
Winrove connects defined workflows with their responsible services. No public API, SDK or developer subscription is currently offered.
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.
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.
Primary account sign-in and callback
Hosted credentials, allowed tenants and callback destinations require confirmation. Enablement is confirmed per organization.
Primary account sign-in and callback
No hosted provider is activated here. Existing-account linking needs independent ownership proof.
Organization authentication restriction
An active organization membership and its SSO policy are both required. Native callback allowlists need verification.
Existing SCIM and lifecycle operations
Supported source handlers must be verified per tenant. A directory update does not grant candidate or personal-record ownership.
Original document storage, signing and protected export
Native signature and portal acknowledgment remain distinct. Provider upload, callbacks and protected downloads need authoritative receipts.
NEXT
Plan a supported integration.
Identify the operation, workspace, required data and intended direction. Confirm permissions, error handling and record ownership before enabling a connection.