> For the complete documentation index, see [llms.txt](https://postica.gitbook.io/binding-system-3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postica.gitbook.io/binding-system-3/overview/pinning.md). # Pinned Paths Put the sources you use most at the top of every bind path menu. Some objects get bound over and over: the player, the game manager, the settings asset, one particular property on one particular material. Hunting for them through the hierarchy every time is friction that adds up. **Pinning** puts them at the top of the bind path menu, everywhere. ## Pinning something

Where	Menu item
A component header, right click	Binding ▸ Pin to Bind Sources
A GameObject in the Hierarchy, right click	Binding ▸ Pin to Bind Sources
An asset in the Project window, right click	Binding ▸ Pin to Bind Sources
Any serialized property, right click	Binding ▸ Pin to Bind Sources, which pins that exact path rather than the object

The same menus offer **Unpin from Bind Sources** on anything already pinned, and **Pin Children to Bind Sources** when what you actually want is everything *under* a path rather than the path itself.

## Using a pin Pinned entries appear in the bind path menu under **Pinned**, above the components of the current source. Click one and you are straight into its members.

Alongside it, **Last Used** lists the sources and pins you reached for most recently, which handles the case where you did not think to pin something but keep coming back to it. Both groups can be turned off in [Visualization](/binding-system-3/reference/settings.md#visualization) if you prefer a shorter menu. Pinning keeps working either way; only the listing goes away. ## Where pins are stored

Pinned thing	Where it is stored
Something in a scene	A `PinnedStorage` GameObject in that scene. Pins travel with the scene, so the team shares them.
A project asset	`global-pins.asset` in the Bindings folder. Project wide.

The bind path menu offers the pins of the current scene plus the global ones, so both sets are always available. ## Reviewing and removing pins **Project Settings ▸ Binding System ▸ Configuration ▸ Pinning** lists every pinned path, grouped by the storage that holds it, and lets you remove them. Paths pinned with **Pin Children** are marked with a **Children** badge, since they behave differently in the menu.

The pinning manager in the settings page

## Pins versus variables They solve neighbouring problems and it is worth being clear about which one you want.

	Pinned path	Bind variable
What it saves you	Navigation while authoring	A concrete reference at runtime
Effect on the binding	None. The binding ends up with an ordinary source.	The binding resolves through the variable every time.
Changing it later	Does not affect existing bindings	Changes every binding that uses it
Good for	The objects you bind to constantly	Prefabs, spawned objects, shared values

In short: a pin is a bookmark, a variable is an indirection. See [Bind Variables](/binding-system-3/overview/bind-variables.md). ## From code ```csharp using Postica.BindingSystem; // Any component or asset can act as pinned storage. IPinnedStorage storage = /* PinnedStorageComponent or PinnedStorageAsset */; storage.AddPath(new PinnedPath(context, "position.x", typeof(Vector3))); storage.RemovePath(existingPath); foreach (var path in storage.AllPaths) Debug.Log(path); ```