# Hand-off Files

> Plan the handover of a departing person's Google Drive files. Paste their file list - a Drive API JSON files list
> (name, path, owners, modifiedTime, permissions), a CSV or tab-separated export with name, folder, owner, modified and
> shared-with columns, or plain "path | modified | shared with" lines - with the manager's address and the leaving
> date. The page keeps the files they own, groups them by folder, finds the colleague who works on each folder most,
> marks stale files and files someone outside can open, and draws a waffle of one square per file. A metered run plans
> each folder - review the sharing first, archive with the manager, transfer to the colleague, or give to the manager -
> and the page checks every action and receiver against its own rule. Nothing is moved from the page. Built on the
> SkillSafe skill @googleworkspace/recipe-transfer-file-ownership.

https://hand-off-files.skillsafe.ai/

## What is free
- Reading lists: Drive JSON (a files list or a bare array; permissions with emailAddress, type anyone and domain), CSV or tab-separated tables with a name column (folder or path, owner, modified and any shared-with, collaborator, editor or viewer columns are used), and lines split by | (the first cell the path, a date cell, cells of addresses).
- Ownership: only files the person leaving owns are planned; with no address given, the most common owner is taken.
- Folders: the first two folder levels. Collaborators on the leaving person's domain are inside; personal mailboxes (Gmail, Outlook and the like), other domains and anyone-with-the-link shares count as shared outside.
- Receivers: the inside collaborator on the most of a folder's files; a tie goes alphabetically. Stale: no edit in the 365 days before the leaving date (or the latest edit, with no date).
- The waffle (PNG, SVG) and a CSV of every file with its folder, date, collaborators, outside shares and plan.
- Three samples (Drive JSON, CSV, plain lines) replay their saved plans at no cost.

## The metered task
One task, `handover`, on gpt-terra, metered per run. Input string fields: `task`, `goal`, `people` (who is leaving and when, the manager, the counts), `folders` (one line per folder, `f1.` ... up to 20: files, stale files, the last edit, who outside can open it, and the inside collaborators with how many files each is on) and `others`. The reply is one JSON object: `verdict` (`ready` or `blocked`), `plan` (each `folder`, `action` - `review`, `archive`, `transfer` or `manager` - `to`, the receiving address, and `why`) and `note`.

The page checks each action and receiver against its own rule (review what is shared outside; archive what is all stale with the manager; transfer to the colleague on the most files; otherwise the manager), refuses a transfer to someone who does not work on the folder, checks the verdict against the sharing, every number and date against the list, and warns on a gendered pronoun.

## Links
- API tutorial: https://hand-off-files.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@googleworkspace/recipe-transfer-file-ownership