Device Sharing

Device Sharing allows one organization to temporarily share a CloudBox with another organization within the RUFUS ecosystem. It is designed as a secure, controlled way to lend devices between timers while maintaining clear ownership, visibility, and operational integrity.

Overview

With Device Sharing, a CloudBox can be temporarily assigned to another organization for operational use.

• The owner organization generates a secure share token.

• The recipient organization uses that token to add the device to their account.

• During the sharing period, the device behaves like a normal CloudBox for the recipient.

This is especially useful for:

• Collaborations between timing companies

• Equipment lending for events

• Backup or overflow device usage

How It Works

1. Owner: Generate a Share Token

Share device

From the CloudBox detail view, the owner:

• Generates a secure share token

• Selects a validity period:

  • 1 day

  • 1 week

  • 15 days

⚠️ As soon as the token is created:

• The device becomes reserved for sharing

• The owner can no longer use it or bind it to events

2. Recipient: Accept the Device

Add shared device

From the Devices page, the recipient:

• Enters the share token

• Adds the CloudBox to their account

Once accepted:

• The device appears like a normal CloudBox

• It is clearly labeled as:

  • Shared

  • Shared by [organization]

  • Expiration date

Device Behavior During Sharing

Full Operational Use

The recipient organization can:

• Attach the CloudBox to races

• Use it in RUFUS Cloud and RRM

• Run live timing sessions

Data Ownership

During the sharing period:

• All sessions, passings, and race actions → belong to the recipient organization

• The owner does not receive or own new data generated during this time

Exclusivity

Device Sharing is exclusive:

• A shared CloudBox is fully controlled by the recipient

• The owner cannot use the device while it is shared

Ending a Share

A share can end in two ways:

Automatic Expiration

• The share ends when the selected TTL (time-to-live) expires

Manual Revocation

• The owner can revoke the share at any time

What Happens When a Share Ends

• Recipient access ends immediately

• The device is:

  • Removed from active race use

  • Prevented from remaining stuck in workflows

• Control returns fully to the owner

Visibility & Status Indicators

The interface clearly shows sharing status on both sides:

Owner View

• Reserved for sharing (token created, not yet accepted)

• Shared out (actively used by another organization)

Recipient View

• Shared

• Shared by [organization]

• Expiration date

These indicators remain visible even when the device is attached to events.

Subscription Limits

Device Sharing respects plan limits:

• Shared devices count toward the recipient’s CloudBox allowance

• If accepting a shared device exceeds the limit:

  • The operation will be blocked

Example:

• A FREE plan user cannot accept a shared device if already at the maximum allowed devices