# Install, first scan and the dashboard

What happens from the moment you install, and what every number on the home screen counts.

## Permissions Snapty asks for

| Permission | What it is used for |
| --- | --- |
| `read_themes` | Reading your live theme's files to record them |
| `write_themes` | Putting a file back when you ask for a restore — and nothing else |

Holding the second permission does not mean Snapty writes to your live theme. It writes to a theme only when you restore something, and to your live theme only for a single file you named and confirmed. See [What Snapty never does](https://docs.foxecom.com/snapty-app#what-snapty-never-does).

## The first scan

The moment you install, Snapty records your live theme. This runs once, and you can watch it on the home screen:

1. **Finding your live theme**
2. **Reading its files**
3. **Recording the first snapshot**

A few hundred files is normal, and so is a minute or two.

That first recording is your **baseline** — the point every later change is measured from. It records your theme as it is today, edits and all. It is not a clean copy of the original theme, and Snapty never presents it as one.

<Hint type="warning" title="If the scan does not finish">

The home screen says so and offers to run it again. Snapty keeps no partial recording: a scan that read only half a theme would look exactly like a theme with half its files deleted.

</Hint>

## The dashboard

The home screen is a status report, not a summary. Every number on it is counted.

### The watch card

The card at the top, with a ring in the corner.

| What you see | What it means |
| --- | --- |
| **Live theme · watching** | Snapty has resolved which theme is live and is recording it |
| **Live theme · not checked yet** | Installed, but no check has completed. Normal for the first few minutes |
| **next check** ring | How far through the current interval you are. **due now** means the next check is imminent |
| **N files, compared daily** | How many files your live theme holds, and how often they are compared |
| **Last check 4 hours ago** | When the most recent check finished — not when it found something |
| **Incomplete · Failed · Interrupted** | The last check did not finish cleanly. The activity log says why |

### Recordings kept · checks run

Two counts beside the card, covering the whole time Snapty has been installed:

- **recordings kept** — how many recordings you can currently open. Recordings that have rolled off are not counted, because you can no longer read them.
- **checks run** — every check since install, including the ones that found nothing.

<Hint type="info" title="These two numbers are meant to disagree">

A store where nothing has changed for a month shows many checks and very few recordings. That is a healthy store, not a broken app.

</Hint>

### Nothing has been recorded yet

If Snapty is installed but has no baseline, the dashboard says so and offers to record your live theme now. Everything else on the screen is still true — what is missing is the starting point later changes are measured against.

### Recent recordings

The most recent entries from your timeline, each with its date and how many files changed. Opening one takes you to the recording; **History** takes you to all of them.

A recording tagged **baseline** is your first one. The tag on the others says what caused the check to record: a scheduled check, a theme being published, a recording you asked for yourself, or one taken automatically just before a restore.

### Your Vault

Your snippets and whether each is switched on. If the Snapty app embeds are off in your live theme, this card says so — that is the state where a snippet is saved, switched on, and still not reaching your storefront. See [Managing snippets](https://docs.foxecom.com/snapty-app/code-vault/managing-snippets#turn-on-the-snapty-app-embeds).

## What the dashboard does not tell you

<Hint type="warning" title="Whether your theme is in good shape">

Snapty knows what has changed since it started watching. It does not know what your theme looked like before that, so *"nothing has changed"* is never a statement that your theme is fine — the baseline recorded it as it was found.

</Hint>

<Hint type="warning" title="Whether a snippet ran">

The Vault card tells you a snippet is stored, published and switched on. It does not claim the code executed on your storefront, because Snapty has no way to observe that.

</Hint>

## Next

<PageLink href="https://docs.foxecom.com/snapty-app/history-and-restore/overview" subtitle="How a check works, what a recording is compared against, and what restoring can and cannot do." icon="fa:clock-rotate-left">
  History & Restore
</PageLink>

<PageLink href="https://docs.foxecom.com/snapty-app/code-vault/overview" subtitle="Keep tracking code and custom snippets outside your theme files." icon="fa:vault">
  Code Vault
</PageLink>