Google Drive is a backup destination for job photos and signed documents, copied one way into a dated folder in your own Drive when a job is completed or an invoice is paid. It is deliberately not a file store for Ormi: Drive is a folder tree with its own sharing model, and pointing Ormi at it as primary storage would give every job photo two owners.
Enable the Google Drive API, then create an OAuth client ID of type Web application. The scopes are drive.file and userinfo.email and nothing else, which keeps the app out of Google’s sensitive-scope review.
Settings, then Integrations, then Google Drive. They are stored against your company and encrypted. The drawer carries the exact authorised redirect URI to paste back into Google, byte-identical.
Press Connect and choose the Google account the files should land in. The next job you complete queues its files; the queue drains every few minutes and the connection shows the last push.
Real workflows, not marketing bullets.
No. Customer email sends from your own domain and needs no Google sign-in at all. This is a file backup, a separate connection with separate credentials, and turning one on does nothing to the other.
No, and the scope is what guarantees it rather than a promise. The drive.file scope reaches only files the Ormi app itself created, so everything else in your Drive is invisible to it and always has been.
Yours. You create the OAuth client in your own Google Cloud project and the files count against your Drive. Ormi holds no Google key of its own for this, so there is no shared quota and nothing to bill back.
Not in this plan. The scoped feature copies files out of Ormi into Drive. Pulling a Drive document into a job is a different feature and is not scheduled.
Yes. Download them from the job, the customer record or the mobile app. Drive is a second copy, not the way out.
$25 per field technician, per month. Dispatchers, admins and owners are free. Your first 15 days are free, with unlimited jobs too.