Connectors

How it works

Only the local test source has self-service setup. External Business sources need administrator configuration and a separate approved pilot; their presence in a catalog is not an active connection.

Before you start

Confirm that the connector is enabled for the workspace and that an administrator has approved the external system, scopes and data direction. Use a dedicated least-privilege account where the provider supports it.

What to do

1. Distinguish the local test source from an administrator-configured external source.
2. Review approved read scope, data direction and retention for the exact external source.
3. Use only the setup offered for that source and bind the intended workspace.
4. Check sync freshness and errors; revoke access when no longer needed.

Verify the result

Credentials must remain in the authorized secret boundary, outside prompts and browser-visible output. A failed synchronization does not justify granting broader access.

If it does not work

For authorization, sync or stale-data errors, check connection status, granted scopes and the last successful run. Reconnect only through the visible authorization flow. Never paste access tokens, client secrets or complete payloads into chat or support.