Safe Archive and Google Drive permissions: a practical checklist
Set the right Google Drive scope, approve the destination, handle native-file exports, and keep access changes separate from the archive copy.
Safe Archive guide
Keep the copy, keep the context, and keep a record of what arrived.
Founder of ARCED Foundation, ARCED International, and Solutions of Things Lab (SoTLab). Built FolderManifest to help teams protect file integrity and stay audit-ready.
Published August 20, 2026
Scope first
Decide what you are allowed to copy before starting the archive.
Copy second
Use a destination that will remain available after access changes.
Verify last
Keep a report that names the files copied, converted, skipped, or failed.
Quick answer
Approve the Google Drive source scope, sign in through the desktop browser flow, confirm the destination account, review native-file exports, and keep ownership or deletion decisions separate from the archive copy.
1. Approve the source before you sign in
Decide which folders and records may be archived before the browser authorization begins. Confirm the owner, administrator, or records policy allows the export. A person being able to open a file does not automatically mean they may retain or move it.
- List the Drive folders and shared locations in scope.
- Separate personal files from company-owned records.
- Record excluded folders and files that need an ownership transfer instead.
2. Sign in once and confirm the destination
Safe Archive uses a one-time browser sign-in for the desktop Drive flow. Before running the copy, confirm the destination folder, receiving account, and access that will remain after offboarding or handoff.
Do not put tokens or passwords in a job file or handoff note. The credential flow keeps authorization separate from the archive report.
3. Review native files and archive exceptions
Docs, Sheets, and Slides are exported to the selected format because Google-native files are not ordinary downloadable bytes. Choose editable office files, PDF copies, or URL pointers when the Drive account will remain available.
Forms and Sites that cannot be exported are recorded as skipped. Open the HTML report and CSV report after the run, then review those exceptions with the administrator or records owner.
4. Keep access changes separate from the copy
Safe Archive copies the selected Drive files and leaves the source unchanged. It does not change sharing, transfer ownership, remove access, or delete the source.
Complete the archive review first. Then handle ownership transfer, account closure, sharing changes, and source retention under the organization policy.
Make the archive reviewable
FolderManifest copies the folder locally or to a supported destination, then creates a report with the files that arrived and the files that need attention.
Frequently asked questions
What permission should I have before archiving a Drive folder?
You should have authorization from the owner, administrator, or records policy for the folders and files being exported. The ability to open a file is not the same as permission to retain or move it.
Does Safe Archive need a separate headless Google login?
No. The desktop workflow uses a one-time browser sign-in and reuses that authorization for the Safe Archive tab or CLI Drive job.
How are Google-native files handled during an archive?
Docs, Sheets, and Slides are exported to the selected format. Forms and Sites that cannot be exported are recorded as skipped in the report for follow-up.
Does Safe Archive change Drive sharing or delete the source?
No. Safe Archive copies the selected files and leaves the source unchanged. Ownership transfer, sharing changes, and deletion are separate administrative actions.