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

# Administered lists

> The generic editor for the smaller closed lists a plant configures once.

Not every list deserves a screen of its own. Nobody wants a bespoke editor for Tool Conditions.

<img src="https://mintcdn.com/assetinfinity/95UxrhuglB-erOSy/images/admin/administered-list.png?fit=max&auto=format&n=95UxrhuglB-erOSy&q=85&s=fb099e3cef8fc16e69c6b94cd4ee6e9b" alt="A generic administered list" width="2880" height="1800" data-path="images/admin/administered-list.png" />

## What is here

The smaller closed lists — tool conditions, skill categories, location types, asset relationship
types and the rest. Administration lists what your deployment can configure and what your roles let
you do to each.

A generic table is not a compromise for these. It is the right answer, and it stays in step with the
product automatically: the list of what exists and the fields each row carries come from the model
itself, so a new list added in an upgrade appears here without anyone wiring up a screen.

## What is deliberately not here

<AccordionGroup>
  <Accordion title="Assets, vendors, contracts, parts">
    Records with their own screens, and they link out rather than being editable in a generic table.
    An asset is edited beside its meters and its work history, because that context is the reason
    the screen exists.
  </Accordion>

  <Accordion title="Anything a module's settings screen owns">
    Priorities, work order types, skills, meter types and so on belong to their module's screen —
    [work](/config/work), [assets](/config/assets), [workforce](/config/workforce) — where they can
    be shown beside the things they relate to.
  </Accordion>

  <Accordion title="Child records">
    A contract's SLA lines, a template's items. These are reached through their parent. A list of
    every SLA line in the organisation, unattached to a contract, answers no question anybody has.
  </Accordion>
</AccordionGroup>

## Editing

Each list gives you search, add, edit and deactivate. The columns come from the record itself, so
what you see is what the row actually holds.

## Deactivate rather than delete

Prefer deactivating. A deactivated entry stops being offered on new records and stays readable on old
ones — a job closed against a resolution code you have retired still shows what it was closed as.

Deleting an entry that existing records use is refused, and the refusal counts the records so you
know what you are dealing with.

## Permissions

What you can do here follows your role. Most configuration needs `admin.configuration` permissions —
System Administrator and Maintenance Administrator by default. See [roles](/setup/roles).


## Related topics

- [Setting up the plant](/setup/overview.md)
- [Sensors and condition alerts](/assets/sensors.md)
- [Root cause and corrective actions](/assets/root-cause.md)
- [The work order list](/work/work-orders.md)
- [Finding your way around](/get-started/navigating.md)