# Use Notion for a document owner gap

Example: A team data source tracks procedure pages. Several pages have an update date but no responsible owner.

By Righthand Team · 2026-10-19

Source: https://www.righthand.ai/blog/use-notion-for-a-document-owner-gap

Keep Notion 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 team data source tracks procedure pages. Several pages have an update date but no responsible owner.

[Provider documentation](https://developers.notion.com/reference/query-a-data-source). The documentation gives information about querying a data source with filters and sorting. Current documentation separates data sources from the older database-query interface.

## Make account access explicit

If Notion 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

> Read the supplied procedure data source.
>
> Send pages with no assigned owner.
>
> Keep update dates with those pages.
>
> Send the owner the result before 3 PM Friday.
>
> Use Pacific time.

## Use the provider records for the result

Identify the exact data source and its property meanings. Use filters for the owner's decision. Follow returned pagination so the report does not treat one page as the complete source.

A recent edit does not establish continuing responsibility.

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

> Three procedure pages have no owner. Their recent dates do not identify who has responsibility for them.

The operations lead gives the pages owners before defining a recurring maintenance responsibility.

## 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 Notion 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).