> For the complete documentation index, see [llms.txt](https://help.runonrufus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.runonrufus.com/rufus-cloud/cloudbox/binding-your-cloudbox-with-the-cloud.md).

# Binding your CloudBox with the Cloud

Binding a **RUFUS CloudBox** to your RUFUS Cloud account allows the device to synchronize with the platform and become available inside **RUFUS Race Manager** for timing operations.

Once bound, the CloudBox can transmit passings, report device status, and participate in live race sessions.

## What Binding a CloudBox Does

Binding a CloudBox connects the device to your **RUFUS Cloud account** using a secure access token.

After binding, the CloudBox will:

* Appear in your **Devices list** in RUFUS Cloud
* Report **device status and connectivity**
* Send **timing passings** to the cloud
* Become available for **assignment to events and checkpoints in Race Manager**

This process activates **real-time synchronization** between the device and the RUFUS ecosystem.

## Generating a Cloud Access Token

To bind a device, you must first generate a temporary **Cloud access token**.

<figure><img src="/files/rKA5D78wWwEXkQOBs2hT" alt=""><figcaption><p>Bind CloudBox Card</p></figcaption></figure>

### Step 1 — Open the Devices Panel

In **RUFUS Cloud**, navigate to:

**Devices → Devices list**

Locate the card titled **Bind your CloudBox**.

### Step 2 — Generate the Token

Click **Generate token**.

RUFUS Cloud will generate a numeric access token similar to:

`64631`

The token includes an expiration time. By default, it remains valid for a limited period (for example, about 2 hours).

If the token expires before being used, simply generate a new one.

### Step 3 — Copy the Token

Click the **copy icon** to copy the generated token.

You will use this token inside the CloudBox device interface.

## Entering the Token in the CloudBox

Once the token has been generated, it must be entered into the CloudBox configuration interface.

### Step 1 — Access the CloudBox Interface

Connect to the CloudBox using one of the following methods:

* WiFi Access Point
* Ethernet connection
* Local network connection

Open a web browser and navigate to:

`cloudbox.local`

or use the device IP address.

### Step 2 — Open the Cloud Configuration Section

In the CloudBox interface, locate the **Cloud** configuration section.

This section allows you to connect the device to RUFUS Cloud.

<figure><img src="/files/Yn0bDGyYCxSEyu3uIoGC" alt=""><figcaption><p>CloudBox Cloud Section</p></figcaption></figure>

### Step 3 — Enter the Token

Paste the access token generated in RUFUS Cloud into the **Cloud access token** field.

Save or apply the configuration.

## Confirming the Device Binding

After the token is accepted, the CloudBox will authenticate with RUFUS Cloud.

Once the connection is established:

* The device appears in your **Devices list**
* The device status becomes visible
* Timing sessions can be created from **Race Manager**

You can now assign the CloudBox to race checkpoints and start capturing passings.

## Token Expiration

The binding token is temporary and only used during the device authentication process.

If the token expires before being entered into the CloudBox:

1. Return to **RUFUS Cloud → Devices**
2. Click **Generate token** again
3. Enter the new token into the device

Once a device is successfully bound, the token is no longer needed.

## After Binding Your CloudBox

After the CloudBox is connected to RUFUS Cloud, the next steps typically include:

* Assigning the device to an event in **RUFUS Race Manager**
* Configuring RFID readers and antennas
* Starting timing sessions
* Monitoring passings and device status in real time

## Learn More

For detailed information about configuring and operating the device itself, refer to the full CloudBox documentation:

**RUFUS CloudBox Help Center**

The CloudBox documentation includes detailed guides on networking, RFID reader configuration, antenna setup, firmware updates, and race-day operational procedures.