> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/product-docs/api-reference/staging-admin-metadata.md).

# Staging Admin Metadata

## Why This Section Is Valuable

This is the best area for removing hardcoded IDs and making request creation more dynamic.

## Key Metadata Entities

* `Technician`
* `User`
* `Site`
* `Support_Group`
* `Department`
* `Category`
* `Subcategory`
* `Status`
* `Level`
* `Mode`
* `Impact`
* `Urgency`
* `Priority`
* `Item`
* `Request_Type`
* `Request_Closure_Code`
* `Tag`
* `Resolution_Template`

## Typical Use In The App

* populate dropdowns
* validate request payloads
* resolve names to IDs before submit
* cache reference data locally
* avoid brittle workflow logic tied to stale config

## Strongest Candidates For Near-Term Use

* `Technician`
* `Support_Group`
* `Category` / `Subcategory` / `Item`
* `Status`
* `Impact` / `Urgency` / `Priority`
* `Request_Type`

## Recommended Integration Strategy

1. fetch and cache metadata
2. resolve human-readable selections to IDs
3. validate before create/update
4. keep fallback logging for unknown values

## Recommended Source

* `document/staging.md`
* `document/api_sdp.md`