> ## 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.

# What is Card Studio?

> Understand what Card Studio builds, who uses it, and how cards go from idea to HubSpot.

# What is Card Studio?

Card Studio is a no-code designer for HubSpot app cards. You assemble a card from building blocks, connect fields and data, add rules or actions, and publish it without writing or deploying any code.

A published card is rendered with HubSpot's own UI components. That means it follows HubSpot's look and feel and the constraints that apply to the chosen placement.

## What can you build?

Typical cards include:

* a customer overview with record fields, stat tiles, and associated deals;
* an onboarding checklist with saved answers and multiple steps;
* an invoice overview with data from an accounting system;
* an approval flow that updates HubSpot and shows a confirmation;
* a contact update form with validated input fields;
* an action menu for notes, tasks, email, or meeting scheduling.

See [Building blocks](/components/index) for the complete list.

## From draft to HubSpot

A card has an editable draft and can have one live version:

1. You create a blank card or start from a template.
2. The designer saves changes automatically as a draft.
3. You preview the card's layout and interactions.
4. When you publish, the card is validated and frozen as a new version.
5. HubSpot automatically fetches the live version the next time the card is opened.

Publishing a new version does not require a new app installation or a new deploy. Read more in [Draft, live, versions, and offline](/cards/lifecycle).

## The three key concepts

**Building blocks** are the visible elements on the card. **Dynamic values** connect them to HubSpot, form answers, associated records, or external systems. **Actions** determine what happens on a click or at the end of a flow.

You can build simple cards with building blocks alone. Use data, rules, and actions when the card needs to adapt to the current record or do work.

## Roles

An **editor** can build and publish cards. An **owner** can do the same and can also manage users, organization templates, and connections that require organization-level access. See [Account, organization, and users](/admin/accounts-users).

## Next steps

Follow [Create your first card](/getting-started/create-first-card) for a complete beginner's guide.