# Organize

> Find any tag in the Unified Namespace, see what depends on what, check the setup for broken links and wasted data, and package objects as templates.

Source: https://proxus.io/docs/organize

**Organize** is about how your setup fits together. Here you find where a value lives in the plant, which rules and
targets use it, what in the configuration is broken or wasted, and how to reuse a set of objects on another hub.
In the hub, these screens are in the **Organize** menu.

## The screens

| Screen | What it is for |
| --- | --- |
| **UNS Explorer** | The Unified Namespace as a live tree: enterprise, site, area, line, device and tag, with the current value, quality and a short trend of every tag. |
| **Health Checks** | Checks every configured object and lists what is broken, what needs a look and what is collected for nothing. **Trace an object** shows what one object depends on and what it feeds. |
| **Application Templates** | Packages devices, profiles, rules, functions and other objects into a template that can be exported, imported and installed. |

Every device, rule, function, dashboard and outbound target also has a **Dependencies** action on its own page,
and Proxus shows what depends on an object before you delete or switch it off.

## Start here

## Background

The structure of the tree comes from the place each device is given: see
[Unified Namespace](https://proxus.io/docs/concepts/unified-namespace). Who may see which part of it is set per role: see
[UNS permissions](https://proxus.io/docs/administer/uns-permissions).