Skip to content
Fenwix
TRVisit Fenwix.app

Planned connector

Planned Google Drive integration architecture

Fenwix does not support Google Drive synchronization today. Google Drive and Shared Drive are the first planned connector target for the Customer-Owned Data Plane. The connector will be considered available only after local encryption, portable record packaging, explicit authorization, conflict handling, recovery and real-provider conformance are implemented and tested.

Planned Google Drive connector flow from a Fenwix record to a customer-controlled folder with revision handling.
ROADMAP

ROADMAP: no production Google Drive sync, Shared Drive connector or OAuth connection is currently offered by Fenwix. This page documents intended design and release gates only.

ROADMAP

Customer-controlled location

The target repository is selected and administered by the customer, not a Fenwix inspection database.

ROADMAP

Protocol before provider

Canonical identity and package format must be defined independently of Google file IDs and paths.

ROADMAP

Gate before claim

Real credentials, interruption, duplicate, conflict and recovery tests are required before availability wording.

Architecture flow

FENWIX DEVICE
      ↓ encrypted local record
FIELD DATA PROTOCOL
      ↓ provider adapter
CUSTOMER GOOGLE DRIVE / SHARED DRIVE
      ↕ authorized Fenwix devices

Why is Google Drive the first planned connector?

ROADMAP

It provides a widely recognized customer-controlled repository and a concrete provider against which the connector contract can be tested. It is a first conformance target, not a special canonical model and not evidence that every provider will behave identically.

  • Customer administrator controls the Google environment
  • Shared Drive can support organization-owned storage scenarios
  • Provider behavior must be verified against current official APIs during implementation
  • Fenwix record identity must not depend on a Google file ID
  • Other providers remain separate roadmap work

What must the connector store?

ROADMAP

The target package represents a structured source record, immutable context, evidence relationships, integrity manifest and payload-hash list. A report PDF can accompany the record as a derived artifact but cannot replace the canonical data.

  • Versioned protocol envelope
  • Canonical record and revision identity
  • Evidence payloads with occurrence context
  • Integrity and transfer hashes kept conceptually separate
  • Provider state such as path, cursor and ETag outside the content digest

How should authorization and credentials work?

ROADMAP

The user must knowingly connect the relevant customer storage and see what the connector can access. Credentials require protected local handling, revocation behavior and a defined response when permissions change or a device is lost.

  • Explicit connection and repository selection
  • Least-privilege scopes validated during implementation
  • No support backdoor into customer storage
  • Credential revocation and reauthorization states
  • Organization authorization cannot be inferred only from storage ACLs

What synchronization failures must be tested?

ROADMAP

A successful upload is the easiest case. Release readiness depends on interruption, retry, duplicate execution, partial package, quota, permission loss, concurrent offline revisions, corrupt payload, provider outage and recovery from a fresh authorized device.

  • Create-if-absent repository bootstrap
  • Resumable and idempotent transfer
  • Explicit conflict rather than blind last-write-wins
  • Bounded recovery scan within the Fenwix root
  • Integrity verification after download
  • Chaos and real-provider conformance tests

What is available now instead?

CURRENT

Fenwix Solo works from app-private local storage and provides explicit report, sharing and backup functions. Those paths are not described as Google Drive synchronization and should be evaluated for the current single-device workflow.

  • Offline local inspection
  • User-initiated export or share
  • Local backup and restore paths
  • No automatic Google Drive data plane
  • No cross-device shared-record promise

Frequently asked questions

Does Fenwix sync inspections to Google Drive now?

No. Google Drive synchronization is not currently available.

Can I connect a Google Shared Drive today?

No. Shared Drive is part of the planned connector target, not a current production connection.

Will Fenwix store copies in its own cloud?

The target Zero-Custody design avoids making Fenwix the default repository for operational inspection content, subject to final implementation and verification.

Will a PDF be the synchronized record?

No. The target uses structured, versioned source-record packages; PDF remains a derived output.

When will the connector be available?

No release date is claimed. Availability depends on completing and verifying identity, encryption, protocol, transfer, conflict, recovery and provider-conformance gates.

Related architecture and product surfaces

Connector status →Storage architecture →Customer-Owned Data Plane →Zero-Custody architecture →Security requirements →

Treat the connector as planned until every gate is proven

Do not plan production operations around Google Drive synchronization yet. Use the current local workflow and evaluate the connector only after Fenwix publishes implemented behavior and verification evidence.

Use the current offline Solo workflow →

Content status: ROADMAP · Last reviewed: 2026-08-16

Claim basis: Fenwix Zero-Custody master plan · Fenwix product decision record · Fenwix.net aligned master brief