> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hubspotcards.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Placements and objects

> Choose the right HubSpot surface and understand which building blocks each placement allows.

# Placements and objects

A card targets at least one object and exactly one placement. The combination determines where the card appears, how much width it gets, and which HubSpot components are allowed.

## The four placements

| Placement in Card Studio | Technical placement  | Best for                                          |
| ------------------------ | -------------------- | ------------------------------------------------- |
| Middle column (tab)      | `crm.record.tab`     | wide overviews, tables, reports, and larger flows |
| Sidebar                  | `crm.record.sidebar` | compact statuses, small forms, and quick actions  |
| Preview panel            | `crm.preview`        | a quick overview without opening the full record  |
| Help desk sidebar        | `helpdesk.sidebar`   | ticket and customer context while working a case  |

The designer shows the card at a width matching the placement. Always check long labels, button rows, and tables at that exact width.

## CRM data blocks in the sidebar

HubSpot does not allow the following Card Studio building blocks in **Sidebar**:

* Property list;
* Associated records;
* Pipeline status;
* Report.

They can be used in the middle column, preview panel, and help desk sidebar. The remaining 18 building blocks can be used in all four placements. The palette dims unavailable choices, and publishing also checks existing blocks.

A regular **Table**, **Chart**, or **Stat tiles** block works fine in the sidebar because they render with standard components. Keep them compact.

## Standard objects and custom objects

The standard objects are contacts, companies, deals, and tickets. For these, Card Studio can offer known labels and demo content even before HubSpot is connected.

On a custom object, you need the object's HubSpot identifier. Once the organization has a HubSpot connection, Card Studio can fetch the real field labels. Without that connection, you can still add fields by their internal name.

## Multiple objects at publish time

The card definition can target multiple object types, and the publish flow can add custom objects. The designer uses the first object as the primary object for the field catalog and preview. So test the card on every targeted object type if the fields differ.

## Switching placement safely

If you want to reuse a card in a different placement, **Duplicate** is often safer than changing the original. The copy automatically removes building blocks the new placement cannot show, and creates an independent draft and version history.