Using Relay for Efficient Team Collaboration

Organize shared work in a workspace

A workspace is the basic unit for organizing team collaboration and granting access in Relay.

Create a workspace for a project, then use it to store Bundles, organize folders, maintain shared Notes and invite the people working on that project.

For example, a model evaluation project can use one workspace to collect:

• Input data and task instructions.
• Reports and logs from each run.
• Results that need a teammate’s review.
• Project conventions and agreed decisions.

Once a teammate joins a workspace, their role determines how they can participate. The invitation grants access to that workspace only; the owner’s other workspaces keep their own membership.

Folders organize content within the workspace. To give different people access to different projects, create separate workspaces and invite members to each one.

The owner manages the workspace

Every workspace has an owner: the account that created it. This is the primary account responsible for that workspace.

The owner creates invitations, assigns roles, removes members and manages workspace settings. Teammates sign in with their own accounts and keep their own identities throughout the handoff.

Uploads in the workspace use the owner’s account storage allowance.

Whether a Bundle is uploaded by the owner, another member or an Agent acting for a member, its storage counts toward the workspace owner’s allowance. Multiple workspaces created by the same owner share that account allowance.

The owner can manage project access and storage centrally while members take part in everyday deliveries.

Invite teammates and choose their roles

The owner chooses a role when creating an invitation. The teammate opens the link, signs in to the same Relay service, reviews the workspace, owner and role, then confirms joining.

Each invitation admits one person and expires after 24 hours by default. The owner can revoke an unused invitation.

Members have either the PUSH or FULL role. The owner has full workspace management permissions.

PUSH members can read and download content throughout the workspace. This role suits everyday contributors who receive tasks, submit outputs and update context.

FULL adds Bundle trash and restore actions, making it suitable for members who also help organize content.

The owner can change roles as the collaboration develops. Members can also leave the workspace themselves.

Give each delivery enough context

Three complementary forms of context support a Relay handoff: the Bundle note, HANDOFF.md and shared workspace Notes.

Bundle notes explain each delivery

Every Bundle requires a short handoff note explaining the files’ purpose, current progress and next step.

Evaluation is complete. report.csv contains the summary and failures.jsonl contains the failure samples. Analyze the failures using the classification rules in HANDOFF.md.

Before downloading, the receiver can see what the delivery contains and what to do next.

With a CLI that supports --save-note, the receiver can choose to save the full note locally as RELAY_NOTE.md alongside the downloaded files. Check relay bundle pull --help before using the option.

HANDOFF.md carries longer task instructions

Multi-step tasks often need more background. The sender can include HANDOFF.md in the uploaded directory and name its location in the Bundle note. The document can describe:

• The task goal and current progress.
• Where to find inputs and outputs.
• The required environment and commands.
• The next action and completion criteria.
• Questions that still need an answer.

An existing task document works too. What matters is that the receiver knows which document to read.

Shared Notes maintain the project background

Shared workspace Notes hold ongoing information such as environment setup, naming conventions, evaluation criteria and agreed decisions.

The Bundle note explains one delivery. HANDOFF.md expands on one task. Shared Notes help members understand the project’s wider working context.

Build a simple receive habit: read the complete handoff note, read the task document it references, then continue with the shared workspace Notes as project background.

A handoff between teammates and an Agent

Suppose Alice and Bob are analyzing a set of model evaluation results.

An Agent uses the workspace permissions of the account it signs in with. Bob’s Agent participates under Bob’s PUSH role.

When Alice returns, she can collect this delivery. History helps the team trace the sender, source device and time; the returned outputs and note explain what work is complete.

Let teammates work on their own schedules

A shared workspace gives members a common place for files and project context. Roles define who handles everyday deliveries, who helps organize content and who manages access and storage.

People and Agents can follow the same handoff process: publish files, explain progress and the next step, read the full context, then return the results to the workspace.

The sender stays connected until upload and publication succeed. The receiver can come online later and continue from the work that has been delivered.