---
title: "Using Buckets in Boards"
url: "https://help.ontraccr.com/en/article/using-buckets-in-boards"
language: "en"
last_updated: "2025-06-08T18:54:09.371Z"
---

# Using Buckets in Boards

## **📋 Using Buckets in Boards**  
 

Buckets can be used in **boards** just like in forms — allowing card fields to pull structured, filtered data from your custom bucket databases.

This enables teams to interact with relevant bucket-linked data directly from board cards.

* * *

## **📋 Where to Configure**

1.  Go to **Settings** → **Boards**
2.  Choose a board and begin customizing one of its **card layouts**

* * *

## **➕ Adding a Bucket Field to a Board Card**

1.  In the card design interface, click **Add Field**
2.  Choose the **“Choose one or more”** field type
3.  Set the **Data Type** to **Buckets**
4.  Select the relevant bucket from your account (e.g. “Contracts”, “Checkpoints”)

✔ The behavior is identical to forms:

-   You'll be selecting from actual entries in the chosen bucket
-   You can use this to link board cards to contracts, equipment, segments, etc.

* * *

## **💡 Use Case**

For example:

-   If your board tracks service calls, you might want to associate each card with a **specific contract** (stored in your Contracts bucket)
-   When a user opens or edits a card, they can pick from real-time, bucket-based options — just like they would in a form

* * *

## **✅ Field Behavior**

-   Selections are live and based on the current state of the bucket
-   Smart filtering applies automatically (see next article)
-   You can use multiple bucket fields per card if needed

* * *

## 🧾 **Summary**

-   Boards support **bucket-linked fields** just like forms do
-   Add a “Choose one or more” field and configure it to pull from a specific bucket
-   Card fields can dynamically reflect real-time entries from your buckets
-   Use this to enable filtering, selection, and deeper data relationships inside your boards

Using buckets in boards allows your teams to interact with structured, filtered datasets directly in the operational workflows they rely on.