> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Environment Data

> Create and manage organizations, domains, platforms, and locations as environment filters.

Under *Administration › Organizations*, *Domains*, *Platforms*, and
*Locations* you create your subscription's environment data. Each entry is also a
value of the environment filter and thereby controls which section of the
inventory is visible.

## The Four Areas

| Area | Purpose |
| - | - |
| *Organizations* | corporate entities within your subscription |
| *Domains* | AD domains, workgroups, system groups, or custom logical groupings |
| *Platforms* | freely definable platforms for classifying your infrastructure |
| *Locations* | physical locations with a hierarchy |

*Organizations*, *Domains*, and *Platforms* share the same layout: a table
with *Name* and *Assets*, row actions *Edit* and *Delete*, a search field,
and a selection column for bulk delete. *Locations* instead builds on a tree
— see below.

<Note>
  The *Assets* column only counts; a click does not lead to the filtered
  list. For deleting, the number is nevertheless decisive, see below.
</Note>

## Creating Entries

All four areas share the same creation dialog. A *Single* / *Multiple*
toggle decides whether one entry or several rows are created at once; when
editing, the toggle is absent.

<Tip>
  In *Multiple* mode, each row carries its own name — so you create a whole
  list of domains or platforms in one pass, instead of opening the dialog
  repeatedly.
</Tip>

<Note>
  The Pro edition allows exactly one organization. Once it exists, *Organizations*
  shows a note with *Change Edition* instead of *Create*. Under this limit, the
  dialog offers only *Single* for organizations. If you delete the organization,
  you can create one again.
</Note>

<Note>
  If the subscription's *Storage* usage limit is exceeded, the controls for
  creating, editing, and deleting are not shown on any of the four pages. The
  lists and the location tree remain readable.
</Note>

<Note>
  A name that already exists on the page is rejected on saving with "Name
  already exists." at the field.
</Note>

## Deleting Entries

<Warning>
  If an entry has at least one asset assigned, *Delete* is disabled for that
  entry. Reassign those assets first — through the assignment on the asset,
  not here.
</Warning>

<Warning>
  In bulk delete, a single affected row locks the whole selection. If deletion
  succeeds only partially, the affected rows alone remain; a line above the
  table then states how many of how many could not be processed, with their
  names. Check that line before you leave the page — it is the only feedback
  on it.
</Warning>

## Locations

*Locations* shows a tree on the left and the details of the selected node on
the right. A location carries a type from a fixed order:

| Level | Next Level |
| - | - |
| Location | Building |
| Building | Floor |
| Floor | Room |
| Room | — |

The type of a new entry follows from the selected parent location and
cannot be chosen directly — *Location Type* is display-only in the dialog.
Creating under a building necessarily creates a floor; without a selected
parent, a top-level location is created.

<Warning>
  *Parent Location* cannot be changed either when editing or when creating
  below a selected node — there the parent is already fixed. The dialog offers
  no way to move an existing location to a different place in the tree.
</Warning>

<Tip>
  The search field above the tree expands all paths to the matches — faster
  than clicking through a deep location tree.
</Tip>

<Note>
  Only a node of type *Location* carries an address (street, postal code,
  city, country, phone); this block is omitted for Building, Floor, and Room.
  In *Multiple* mode, each row carries its own address.
</Note>

<Warning>
  An address field left empty deletes the previous value on save — the dialog
  always sends the whole address block, never a single field.
</Warning>

Each node shows two metrics on the right, *Assets* and *Child Locations*. A
location with child locations but no assigned assets stays deletable — the
lock applies only through assigned assets. There is no bulk delete for
*Locations*.

## Related

You assign organization and location when [creating an
asset](/docs/en/assets/create). Which types and fields exist at all is set by the
[data model](/docs/en/settings/data-model).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.