# A functional test of a Righthand project name shared by two organizations

Test: Supply two fictional project folders named Launch with different customer names.

By Righthand Team · 2026-10-24

Source: https://www.righthand.ai/blog/test-a-righthand-project-name-shared-by-two-organizations

An agency wants source material from one customer's project rather than every project with the same title.

This article is from Righthand. The test inputs and example result are illustrative. No test in this article has an executed result.

## Prepare the test case

Supply two fictional project folders named Launch with different customer names.

A Righthand has its own phone number and email address, with text, email, phone, and Slack communication. [Introduction](https://docs.righthand.ai/introduction).

The initial test uses supplied information and the Righthand's own email. For direct account work, a separate available connection operation is necessary. [Connections](https://docs.righthand.ai/guides/adding-your-first-connection).

## Give the task instructions

> Compare supplied customer and folder context.
>
> Use only the identified customer's source.
>
> Send missing customer identity as a question.
>
> Send the owner the result in this conversation.
>
> Use Pacific time for the supplied deadline.

Identify any permitted outward action explicitly. With **Ask**, the instruction or approval must identify its recipient and task. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## Examine an illustrative result

> The report uses one customer's approved source and does not include the other folder.

The owner gives exact customer context for future source requests.

## The acceptance conditions

The result must keep organizational identity as well as the project name.

Compare the result with the original case information. Examine the teammate's received message when contact is part of the task. A send record and recipient-visible receipt are different observations.

Combining both folders because the titles are the same fails the test.

If the result fails an acceptance condition, stop that responsibility at this scope. Examine [Activity](https://docs.righthand.ai/guides/working-with-your-righthand) for questions, account problems, or the actual communication.

Give the missing source or owner decision before another attempt. If sending has an uncertain result, establish what occurred before repeating it.

## Keep a small test record

Record the task instructions, source information, received result, and owner decision. Record the configured communication policy and applicable connection permissions.

## Select the next task

A direct record, existing app function, or human teammate can be sufficient when no continuing conversation or coordination is necessary. A Righthand is an alternative when the owner wants responsibility for the next steps and decision handoff.

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