# Use Google Drive for an event handout version decision

Example: A trainer shared a folder with two handouts. The printed program identifies an earlier title than the latest handout.

By Righthand Team · 2026-10-18

Source: https://www.righthand.ai/blog/use-google-drive-for-a-event-handout-version-decision

Keep Google Drive as the source for its records. A Righthand can use available information for the decision below.

This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.

## The customer task

A trainer shared a folder with two handouts. The printed program identifies an earlier title than the latest handout.

[Provider documentation](https://developers.google.com/workspace/drive/api/guides/search-files). The documentation gives information about file searches by name, folder, and other supported conditions. Search results depend on account access.

## Make account access explicit

If Google Drive is available in [Connections](https://docs.righthand.ai/guides/adding-your-first-connection), connect the intended account. Give the Righthand access to that connection.

Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.

For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.

[Connection Permissions](https://docs.righthand.ai/guides/add-a-connection) gives information about account access and tool permissions. Give only the access necessary for the identified task.

## The request to the Righthand

> Find the supplied handout files.
>
> Compare titles with the accepted program.
>
> Send the version difference to the course owner.
>
> Send the owner the result before 3 PM Friday.
>
> Use Pacific time.

## Use the provider records for the result

Identify the source folder and search conditions. Exclude trashed files when current material is necessary for the task. Compare returned file names with their folder and context.

The newest file does not necessarily have publication approval.

For a permitted write, examine the resulting account record. A proposal does not establish a completed change.

For an external message, identify the recipient and permitted task. **Ask** uses an explicit instruction or approval. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## An illustrative result and next step

> The latest file changes the handout title and one exercise. The accepted program still names the earlier version.

The course owner gives a decision about which version to send and whether to correct the program.

## Try one account task

1. Give the Righthand one identified source record.
2. Compare its result with that source.
3. Examine the account record after a permitted write.
4. Examine the work in [Activity](https://docs.righthand.ai/guides/working-with-your-righthand).

If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.

## When the account tools are sufficient

Use Google Drive directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.

[Compare plans](https://www.righthand.ai/pricing). [Get a Righthand](https://teams.righthand.ai).