Sync, scope, and role access
Limit imported content, choose change detection, assign role access, and operate connector syncs.
Connector settings are organized into Connection, Sync, Scope, and Permissions.
Sync strategy
Prefer a provider's delta or changes strategy when available. It processes changed and deleted items after the initial import instead of rebuilding every document. Scheduled scans for filesystem-style providers compare source identity, modification data, and persisted sync state so unchanged documents can be skipped.
Choose Manual only when imports must happen solely after an operator starts them. Interval controls are shown only for scheduled strategies.
Source scope
| Mode | Behavior |
|---|---|
| All folders and files | Import every item visible to the connector account |
| Allowlist | Import only selected identifiers and their permitted descendants |
| Denylist | Import visible content except selected identifiers |
Use the searchable provider-folder list when available. Full provider paths are shown so similarly named folders remain distinguishable. Freeform identifiers are available for providers that cannot list folders through their API.
Changing scope can remove knowledge that is no longer included. Review the affected folders before saving and check the next sync result.
Role access
For every role, assign the minimum connector scope needed:
- Search permits the connector's content to participate in search.
- Read adds document, preview, link, and original-file access.
- Write includes read and is reserved for provider integrations that support write operations.
- No selection means no connector access for that role.
Source ACLs remain an additional boundary. Granting a role Read does not override a source file that denies that user's principals.
Start, stop, and delete
- Start sync queues the configured import.
- Stop sync requests cancellation of an active run.
- Delete removes the connector after confirmation and can remove its synchronized knowledge from CogLake. It does not delete the provider's original files. Review the displayed consequences before confirming.
Use Diagnostics to inspect recent jobs, retry processing, and repair selected index entries.
Understand progress and changes
The first import establishes the selected content. Later runs use the provider's available change information or compare the selected files. A scan can examine many items while reprocessing only new or changed content. Renames, moves, deletions and changed source access can also affect what remains visible after a successful sync.
Do not compare a folder count with a file count. Skipped can include unchanged or unsupported content; inspect the job's reason and failed-document details before deciding that a large skipped count is an error. Connected describes access to the source, not completion of an import. Setup required means the wizard still needs to be completed and saved.
After a revoked or expired authorization, reconnect the existing instance with the intended account, verify scope and run a sync. Do not create duplicate connectors as the first remedy. See connector troubleshooting.