Google Drive Invoice Sync: Permissions and Access Checks Source: https://www.getinvoiceagent.com/integrations/secure-google-drive-invoice-sync Reviewed: 2026-09-30 | Owner: InvoiceAgent editorial team Use this access-review record for your own billing process. It is not a security certification, legal opinion, or prescribed retention policy. Never record tokens or passwords. WORKED REVIEW SCENARIO Finance / Client invoices sits inside a parent used by several collaborators. The records owner checks the destination and an actual PDF for unexpected access before handing records to the appointed bookkeeper. They verify invoice 1062's content and sharing, then record the handoff owner. On retirement they disconnect in InvoiceAgent, review authorization in the Google account, and manage retained PDFs separately. YOUR ACCESS REVIEW Reviewer / review date: ___________________________________________ Billing records owner: ____________________________________________ Connected Google account: _________________________________________ Destination name / path / link: ___________________________________ Consent request reviewed by: ______________________________________ People or groups who need records: ________________________________ Folder / parent / sample PDF access checked: ______________________ Unexpected access / resolution: ___________________________________ Representative invoice number / content check: ____________________ Bookkeeper handoff owner / date: __________________________________ Recordkeeping policy reference / next review: _____________________ Disconnect needed / completed: ____________________________________ Google authorization review needed / completed: ___________________ Retained or removed remote PDFs / owner: __________________________ Next action / responsible person: _________________________________ CHECK BEFORE COPYING RECORDS [ ] Intended account and records owner identified [ ] Actual Google authorization request read [ ] File and broader metadata access considered separately [ ] Destination opened from account Integrations and verified [ ] Folder, parent context, and actual PDF access reviewed in Drive [ ] Unexpected access resolved before the records handoff [ ] PDF content checked against the intended invoice [ ] Older copies included after a folder change [ ] Offboarding actions and records owner documented CONNECTION LIMITS Current requested scopes: drive.file and drive.metadata.readonly. A chosen destination does not restrict all metadata access to that folder. Upload does not create a public-sharing permission, but existing destination access still needs review. Sent-only versus sent-and-paid timing is an archive eligibility choice, not a people-access control. Disconnect clears the local connection and invoice file links. It does not delete Drive PDFs or issue Google token revocation. Changing destination affects future uploads. Earlier PDFs stay in their old locations. Before reconnecting and syncing, check for existing copies to avoid rebuilding a duplicate archive. RELATED RESOURCES Drive connection and folder setup: https://www.getinvoiceagent.com/integrations/google-drive-invoice-integration Archive eligibility and recovery: https://www.getinvoiceagent.com/features/google-drive-invoice-sync Client document handling: https://www.getinvoiceagent.com/guides/secure-invoice-delivery Official Drive scopes: https://developers.google.com/workspace/drive/api/guides/api-specific-auth Official Drive sharing: https://developers.google.com/workspace/drive/api/guides/manage-sharing