Google Drive Integration
Google Drive integration lets DBModeler store and sync project files in your own Drive space using an OAuth 2.0 PKCE browser flow.
How it works
Section titled “How it works”DBModeler authenticates directly against Google endpoints, then uses Drive APIs to read and write project files.
The integration is designed for browser-only operation, so there is no separate backend token broker in the normal flow.
What is stored
Section titled “What is stored”Google Drive storage is used for project files and sync metadata relevant to that provider workflow.
DBModeler also tracks sync state locally so it can detect changes and handle conflicts safely.
Sync behavior
Section titled “Sync behavior”When a project is cloud-backed, DBModeler compares local and remote state before writing.
This supports:
- regular provider sync
- conflict detection
- merge workflows when local and remote state diverge
Authentication notes
Section titled “Authentication notes”Google Drive uses OAuth with PKCE and can persist refresh-token-backed access through the secret manager when available.
If the build is missing the required Google configuration, the provider will not be usable.
When to use Google Drive
Section titled “When to use Google Drive”Google Drive is a good fit when you want:
- your project files in a personal or shared Google ecosystem
- provider-backed continuity across machines or browser sessions
- browser-first storage without a Git workflow
Next: OneDrive Integration