Secure credentials
OAuth credentials and tokens stay server-side and are never handed to the AI model.
The target experience is secure authorization, metadata discovery, reviewable AI-assisted mapping, deterministic create/update/upsert, prefill, file attachment, logs, and retry handling. Until that acceptance suite passes in production, use Alvorant Connect APIs/webhooks or join the native-connector validation path.
OAuth credentials and tokens stay server-side and are never handed to the AI model.
AI may propose field mappings, but users review them before deterministic connector code runs.
Authentication, metadata, read/write, rate-limit, error, logging and tenant-isolation tests must pass before Available status.
Do not market Salesforce as a live native integration or paid add-on until the connector is enabled in the live provider registry and its acceptance suite passes. Pro includes native-CRM entitlement as validated connectors become available.