Every integration extends the same cloud.storage.provider model and registers its platform through provider_type. No changes to the base module are required when you add a new vendor — the File Manager, folder rules, sync queue, and attachment hooks work automatically once the provider module is installed.

Works today with: Google Drive, Dropbox, Amazon S3, OneDrive / SharePoint — and any future provider that follows the same dispatch contract.

The engine resolves cloud operations dynamically: _{provider_type}_{operation}. Examples: _google_drive_upload_file, _dropbox_move_file, _amazon_s3_delete_file, _onedrive_create_folder. Upload, download, delete, rename, move, and copy all flow through the same queue and cron — regardless of which API sits behind them.

Building a new connector means implementing the provider-specific methods; orchestration, retries, logging, and UI stay in the base module.

Attachment create/write/unlink hooks, folder rule generation, capability flags, webhook routes, and the OWL File Manager are all provider-neutral. When a user uploads from Odoo or moves a file in the dashboard, the base engine enqueues the job and delegates the actual cloud call to the connected provider module — keeping Odoo behavior consistent while each platform handles OAuth, paths, parents, webhooks, and quotas on its own terms.

Configure multiple cloud accounts side by side — one provider per storage backend, each with its own credentials, root folder, and sync metrics. Users switch providers in the File Manager without leaving Odoo; operations always route to the correct integration through the active provider record. Add or replace cloud platforms over time without rebuilding your document workflow.