Start a handover

This guide starts a Handover run that inventories an outgoing fund administrator’s shared Google Drive folder without changing its contents.

Before you begin

You need:

• an authenticated Infra One account that belongs to the receiving organization;
• organization-admin access, which provides the manage_fund_handovers capability;
• Handover rollout access for the organization or your user account;
• permission to share the intended Drive folder with the service-account address displayed by Handover;
• one folder for the fund or vehicle whose completeness you want to evaluate.

Share only the intended folder. The service account has Drive read-only scope and does not impersonate a user, but Handover will copy supported files it can read into Infra One storage, subject to the documented limits and safety rules.

Select the organization

1. Open https://handover.infra.one from an approved direct link.
2. If prompted, complete sign-in on Venture. While Infra One returns you to the original Handover path and query string, Venture can briefly show Finishing sign-in… with You’ll be redirected automatically. If automatic navigation does not continue, under Not redirected?, select Continue to your destination.
3. At No organization selected, use the organization selector to choose the receiving organization.
4. Confirm that the app opens Handovers for that organization.

The organization selector cannot be dismissed at the host root. It filters by membership and rollout state, not by the Handover management capability. If an organization appears but access is denied after selection, confirm that your account is an organization admin.

Share the Drive folder

1. Select New handover.
2. Under 1. Share the folder, locate: In Google Drive, share the handover folder with the service account as viewer:
3. Select Copy address.
4. In Google Drive, share the handover folder with that exact address as Viewer.
5. Wait for Drive to finish applying the permission before returning to Handover.

Do not share an entire Drive or a broader parent folder merely to make the run succeed. Handover recursively reads all content reachable beneath the submitted folder.

If the page says The handover service account is not configured for this environment — runs cannot be created., stop and ask the environment owner to configure Handover. There is no address you can safely substitute.

Start the run

1. Under 2. Paste the folder link, enter the value in Drive folder link. You can paste a folder URL such as https://drive.google.com/drive/folders/…, a scheme-less Drive folder URL, an open?id= folder URL, or the bare folder ID.
2. A shortcut is accepted when it resolves in one hop to a folder. Do not submit a file URL or a shortcut to a file.
3. Select Start handover.
4. While Handover validates access, the control shows Checking the folder….
5. When validation succeeds, Handover creates the run and opens its detail page.

The run name comes from the Drive folder name and is truncated to 255 Unicode code points. Handover refuses another active run for the same folder in the organization. That protection is an application check, so do not submit the same folder concurrently in separate sessions.

Understand what Handover collects

Handover walks folders recursively. It follows folder shortcuts without looping and reads file shortcuts by their target. Google Docs, Sheets, Slides, and Drawings are exported to PDF. Ordinary supported files are downloaded in their existing format.

The run stores copies in Infra One; it does not write to Drive or create fund records. Active HTML, SVG, and XML content is stored as an inert download, and executable or script-like extensions are blocked. ZIP and macro-enabled Office files can be stored and probed, but files inside nested archives are not separately inventoried.

Success check

The new run opens with its Drive folder name and a run status such as Queued, Walking folder…, or Fetching files…. The Files found count can increase as discovery proceeds. Let the run reach Completed before interpreting its checklist or downloading a request list.

Completed confirms that discovery settled and the checklist was committed. It does not guarantee that every file was stored, readable, or sufficient.

Troubleshooting

• That does not look like a Google Drive folder link. Paste a supported folder URL or the bare folder ID, without extra prose.
• The folder is not shared with the service account yet — share it with <email> as viewer, then try again. Share the folder with the displayed address as Viewer, wait for Drive to apply the permission, and retry.
• The folder is not readable by the service account. Recheck the exact account, folder, and permission. This fallback can appear when Drive does not provide a more specific reason.
• That link points to a single file — paste the link of the folder that contains the handover. Open the containing folder and submit its link instead. A shortcut to a file is also rejected at the root.
• A run for this folder is already in progress — open it from the handovers list instead. Return to Handovers and open the active run. Wait for a terminal state before using Re-run.
• Google Drive is rate-limiting requests right now — try again in a minute. Wait at least a minute, then submit the same folder again.
• The handover service account is not configured for this environment. Ask the environment owner to configure the service account before retrying.
• Something went wrong while checking the folder — try again. Retry once. If it repeats, note the time and exact message, then share the organization and folder ID only in an approved private support channel. Never copy private file names into support.

Related pages

• Handover overview
• Review a handover and export a request list
• Handover permissions and states
• Troubleshoot Handover