Document Gateways
Document Gateways are separately selected commercial offerings for FormKiQ Advanced and Enterprise. They provide structured ingestion from external sources into FormKiQ's document, metadata, workflow, and governance model.
Gateways bring documents into the platform. Capability modules extend processing and discovery after ingestion, while Integration Frameworks connect documents to business records and systems of record.
Gateway types
| Gateway | Ingestion scope |
|---|---|
| Microsoft Office and SharePoint | Capture documents from Microsoft 365 workflows and SharePoint libraries, with metadata mapping and configured event-driven ingestion. |
| Google Drive and Workspace | Capture documents from shared drives or selected Drive locations, map metadata, and configure conversion of native Google formats where required. |
| Ingest attachments and selected message metadata, then classify and route incoming documents. | |
| Secure File Transfer | Ingest from SFTP or managed transfer environments using schedules or configured events, file metadata, and manifests. |
| Document Scanner and Capture | Connect scanner and capture systems to OCR, metadata extraction, and configured document intake. |
| Cloud Storage | Ingest historical collections or ongoing arrivals from sources such as Azure Blob Storage or Google Cloud Storage. |
The selected gateway and implementation define supported source versions, event handling, synchronization direction, format conversion, and metadata behavior. Ingestion does not by itself provide real-time co-authoring, cross-system comment synchronization, or identical permissions across systems.
Plan the intake workflow
- Select source locations, document categories, and the historical or ongoing intake scope.
- Agree source credentials, API permissions, network access, provider limits, and ownership.
- Map source identifiers, document metadata, and destination sites or workspaces.
- Define duplicate detection, reconciliation, version handling, and retry behavior.
- Configure routing, OCR, mappings, and workflows as required.
- Verify access controls, source traceability, failure monitoring, and operational recovery with representative documents.
Availability and responsibilities
Confirm the gateway license, supported backend and source-system versions, required AWS resources, external-provider charges, and implementation scope during onboarding. Source-system access and FormKiQ document access are separate controls; map and test both.
A gateway may use other licensed modules, such as AI Processing and Analysis, but selecting a gateway does not automatically include every processing capability. External services can process or retain information under their own terms.
See editions and licensing, the gateway overview, and migration planning.