Google Drive integration

Import selected Google Drive files into ClientProof

Choose a Drive file for a ClientProof project. Import a frozen copy for controlled review or attach a live Drive link when the source should keep changing.

  • Selected-file access
  • Frozen copy or live link
  • No continuous folder sync
Synthetic ClientProof Google Drive selected-file import workflow
Product previewCurrent synthetic selected-file Google Drive import flow; it does not imply continuous folder synchronization.

What changes

One client-facing system, three visible outcomes

ClientProof keeps the public project context, private review action, and retained decision record distinct—so clients know what to read and what to do.

01

Choose one file

Import starts from an explicit user selection rather than mirroring the whole Drive.

02

Choose the behavior

Use a frozen copy for controlled review or a live link for an evolving source.

03

Approve the stored version

An imported copy can enter the same exact-version decision workflow.

Drive workflow

Move from storage to a deliberate client delivery step

Google Drive remains the file source. ClientProof adds project context and the decision journey.

  1. Connect Google

    Authorize the Drive account from ClientProof settings.

  2. Choose a project

    Open the client project that should receive the file.

  3. Select the file

    Use the Google picker to choose the intended source.

  4. Import or link

    Create a frozen project copy or keep a live Drive reference.

Import modes

Frozen copy and live link solve different jobs

Use the mode that matches whether the file should be immutable for review or continue changing in Drive.

Google Drive import modes in ClientProof
NeedFrozen copyLive Drive link
File behaviorStored project versionOpens the current Drive source
Exact-version approvalAppropriateNot an immutable ClientProof version
Source updatesDo not alter the imported copyRemain visible through the Drive link
Best useApproval and retained evidenceReference material that keeps changing

Integration boundary

Keep Drive for storage; add ClientProof where delivery needs structure

The integration does not attempt to replace Google Drive or silently mirror it.

01

Controlled approval

Import the intended file as a stored version before requesting a client decision.

Best for: Final or checkpoint files

02

Living reference

Attach a Drive link when the client should always open the latest source.

Best for: Working documents and evolving folders

03

Drive-only collaboration

Stay in Google Drive when comments, editing and file storage are the entire workflow.

Know before you start: ClientProof adds value only when project context or explicit approval is needed.

Buyer questions

Decide with the tradeoffs visible

These answers describe the product as it works today. They do not assume features that are not in the current ClientProof code.

Does ClientProof sync every file in my Google Drive?

No. The implemented workflow uses selected-file access. You choose the file and then choose whether to import a frozen copy or attach a live link.

Can I approve a live Drive link as an exact version?

A live link can change outside ClientProof, so it is not the same as a frozen stored version. Import a copy when exact-version approval evidence is required.

Do clients need a ClientProof account?

No. Clients can open the shared project page and private review links without creating a ClientProof account. A formal decision is confirmed by a code sent to the assigned reviewer email.

Is a ClientProof receipt a digital signature?

No. It is operational approval evidence: the exact file version, assigned reviewer, decision, timestamp, verification method and receipt reference. It is not presented as a digital signature or contract.

Start with one real project

Connect Drive and import one real delivery file

Start with a single project and verify that the selected-file workflow matches the way your team stores and approves work.