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

# Draft, live, versions, and offline

> Understand autosave, published versions, rollback, and how to take a card out of service.

# Draft, live, versions, and offline

Card Studio separates ongoing editing from what users see in HubSpot.

## Draft

The designer saves changes automatically. A draft can be empty or temporarily invalid while you work. It does not affect the live version.

The **Saving...** status means a change is waiting to reach or is on its way to the server. **Saved** means the draft's current revision has been stored.

## Live

A card goes live when you publish it. Publishing validates the draft, requires at least one building block, and creates a new, immutable version.

Only one combination of object and placement can be occupied by a live card in the organization. This prevents ambiguity about which card HubSpot should show.

## Versions

Every publish gets a sequential version number, a timestamp, and, when available, the name of the user who published it. Open **Versions** from a live card on the dashboard.

The version list shows which version is live. The draft does not appear as a published version until it is published.

## Roll back

Choose **Roll back** on an earlier version to make it live. This action:

* moves the live marker immediately;
* does not change the draft in the designer;
* does not delete any newer versions;
* lets you roll forward again by selecting a newer version.

Rollback is therefore a safe operational mechanism, but not a way to replace the draft's content. If the draft should also match the old version, recreate or adjust it separately.

## Take a card offline

Choose **Take offline** on the dashboard. HubSpot can then no longer resolve the card as live, but the draft and versions are kept.

Take a card offline when it needs to be replaced by another card in the same slot, or when the feature should be hidden temporarily. Publish it again to create a new live version.

## A safe change routine

For larger changes, we recommend this order:

1. duplicate the existing card;
2. build and test the change in the copy;
3. take the old card offline during a short maintenance window;
4. publish the copy;
5. roll back or republish the old card if the check in HubSpot fails.
