Google Drive Attachments

It cannot see files it did not create. The module asks Google for the drive.file scope, which limits it to its own uploads. Documents already sitting in your Drive stay where they are. Adopting those needs the full drive scope, which puts the app through Google's OAuth verification and a yearly security assessment.

It does not sync back. Renaming or moving a file inside Drive does not update Odoo. This is one directional on purpose: two way sync makes a deletion destructive at both ends, and a folder tidied up in Drive should not quietly remove an Odoo attachment.

New large attachments do not go straight to Drive. They land in Odoo first and the migration cron moves them afterwards. Odoo's browser upload path would need your Google token in the browser of everyone who attaches a file, so it is switched off while Drive is the provider.

Downloads use your server's bandwidth. They pass through Odoo rather than redirecting the browser to Google. That is what keeps them private and subject to Odoo's access rights, but the bytes do travel through your server.

It does not choose what gets migrated. Odoo's own cron decides that: the models you select, above the minimum file size, older than seven days, and not on models whose code reads the bytes. Odoo generated files such as reports and Sign documents are outside its scope, not this module's.

It covers chatter attachments, not the whole filestore. Odoo 19’s cloud_storage is scoped to files attached through the chatter, above a minimum that defaults to 20 MB. Binary fields such as product images and company logos are never in scope, and Odoo excludes every model whose own code reads the bytes — which in Community means account.move , account.payment , hr.employee , hr.expense , hr.leave and hr.applicant . So invoices, bills, payments, employee files, expense receipts and CVs stay on local disk. If moving the entire filestore is what you need, this is not that app.