# Scopes and scans

> Choosing what a diagram covers, and starting the one-time scans that build it.

A **scope** decides what Continuum looks at within a connection: which regions
or subscriptions, and which resource types.

## Choosing a scope

> [!TIP]
> Scope to the thing you are explaining, not to the account. An unscoped
> account produces a diagram of everything in it, which is unreadable.

The caps are per tier:

| | Team | Enterprise |
| --- | ---: | ---: |
| Cloud connections per owner | 3 | unlimited |
| Scopes per integration | 3 | unlimited |
| Resources per integration | 200 | unlimited |

## Scans are one-time, on every tier

> [!IMPORTANT]
> **Scheduled polling is not available on any plan.** Continuum runs one-time
> scans that you start. When the scheduled poller ships it unlocks on
> Enterprise first.
>
> If you try to enable polling you will be told it is an Enterprise feature.
> No upgrade turns it on today.

## Reading a run

Each run is kept, so you can compare two points in time.

A run reports what it found, what changed since the previous run, and anything
it **could not read**. Permission errors are reported there instead of
producing a smaller diagram with no explanation. Check that list before
concluding something was decommissioned.