# Scopes



A **scope** is the context a session works in. You confirm it once, when the session starts, and everything the session knows about your world comes from it. Each scope has its own mark: one hexagon is you, three hexagons are the team, the planet is a space.

<ScopeFigure />

## Team / Space [#team--space]

Each team owns a color, and everything that belongs to it (its spaces included) carries that color through the interface. Because different teams can have spaces with the same name, a session always names its environment as `Team / Space`:

<EnvironmentExample icon="rocket" color="indigo" team="Northwind" space="Launch site" />

Private is the exception: it's yours alone, so it stays neutral, with no color of its own.

<TeamColorRow />

## The context inventory [#the-context-inventory]

Whenever you pick a Team or Space, Knosy shows the **context inventory**: the list of context files that scope brings to a session. It's there so you always know what a session will know.

The inventory is read-only: it's where you see what a session will load, not where you edit. Only files you've explicitly added to Knosy appear here; everything else on your machine is invisible to it. See [Privacy](/docs/privacy) for what syncs and what stays local.

## A scope belongs to one session [#a-scope-belongs-to-one-session]

Once confirmed, a session's scope never changes. Picking a different Team or Space later affects only the sessions you start afterwards, so two sessions running side by side can never mix contexts.

## Suggested scope [#suggested-scope]

Knosy remembers the last scope you confirmed for each host and folder, and suggests it the next time you start there. A suggestion is just that: it's never applied without your confirmation.