# How it works

A variable is a named, typed value stored as Confluence content, either in a space or in the Capable Asset Store for global variables. Pages refer to it by its ID, never by its name, so renaming is always safe. Each time a page loads, the value is read fresh, as the person viewing the page, which is why a change reaches every page at once and why a reader without access sees a placeholder instead.

The pages below cover each part of that in turn.

---

## In this section

### [Space and global variables](https://help.gocapable.com/variables/space-and-global-variables.html)

Where a variable lives.

### [Variable types and values](https://help.gocapable.com/variables/variable-types-and-values.html)

Text, Number, User and Date.

### [Variables catalogue](https://help.gocapable.com/variables/variables-catalogue.html)

Browse, search and create.

### [Details sidebar](https://help.gocapable.com/variables/details-sidebar.html)

Value, usage and editing.

### [Edit access and version history](https://help.gocapable.com/variables/edit-access-and-version-history.html)

Who can edit, and past values.

### [How a value appears on the page](https://help.gocapable.com/variables/how-a-value-appears-on-the-page.html)

What readers see.

### [Insert a variable from the byline](https://help.gocapable.com/variables/insert-a-variable-from-the-byline.html)

Add a variable without the editor.

### [Who can see a value](https://help.gocapable.com/variables/who-can-see-a-value.html)

Values follow space permissions.

---

## Related

### [Variable macro](https://help.gocapable.com/variables/variable-macro.html)

The macro on the page.

### [Reference](https://help.gocapable.com/variables/reference.html)

Limits and gaps.

---

_How it actually behaves._