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

# Databases overview

> Ingest assets and configuration items from any source, and reference them in tickets, workflows, and more.

Serval uses databases to read and write data from workflows, skills, tickets, campaigns, and journeys. Each database can hold one or more tables, each of which contains one or more items. An item is a single table row with typed fields like text, dates, numbers, or references to other items.

<Note>
  **"Items" and "Entities" are interchangeable terms.** Both terms are used in relation to Serval databases. Item is the term used in the UI that refers to a single row in a database table. Entity is the technical term used in the workflow code, API, and field types.
</Note>

## Database features

* **AI-native ingestion.** Describe a new ingestion in plain English ("ingest all computers from Kandji") and Serval generates the requisite workflow. Serval also suggests how external fields map to your schema, so you review and accept instead of wiring mappings by hand.
* **Multi-source per type.** One item type can pull from many sources. Sync a computer's specs from your MDM and its financial data from your procurement tool. Pick the source of truth per field.
* **Context graph.** Relationships between items are first class, traversable, and visible. See every device downstream of a server, every license assigned to a user, the full dependency chain of a CI.
* **Connected to the rest of Serval.** Workflows read and write items. Skills surface item data to the Help Desk Agent. Campaign responses can be written to databases. See every ticket associated with an item.
* **Full provenance.** Every change to every field is recorded with author, source, and timestamp. Trace what changed and when, even as assets move between owners.

## When to use databases

* **Single source of truth for hardware, software, and licenses.** Pull from your MDM, procurement tool, and IdP into one schema. Pick the source of truth per field. Track provenance through every transfer.
* **CMDB for change management and impact analysis.** Model CIs and their relationships as item types. The context graph traces downstream dependencies. Workflows can fire when an upstream CI changes.
* **Reference data for tickets, catalog items, or workflow state.** Any item type can back custom ticket fields, catalog reference options, journey metadata, and persistent workflow state.

## What you can do with Databases

<CardGroup cols={2}>
  <Card title="Design your schema" icon="table" href="/sections/documentation/databases/schema-design">
    Define item types, fields, and relationships. Evolve the schema as your needs change.
  </Card>

  <Card title="Ingest from any source" icon="cloud-arrow-down" href="/sections/documentation/databases/ingestion">
    Pull data from connected apps with AI-suggested field mappings, multi-source reconciliation, and scheduled syncs.
  </Card>

  <Card title="Browse and query" icon="magnifying-glass" href="/sections/documentation/databases/browsing-and-querying">
    Filter, sort, save views, and traverse the context graph.
  </Card>

  <Card title="Use it everywhere" icon="link" href="/sections/documentation/databases/administration#help-agent-visibility">
    Reference items from workflow code, surface them to the Help Desk Agent, and report on them in dashboards.
  </Card>
</CardGroup>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Build your first database" icon="play" href="/sections/documentation/databases/quickstart">
    Define an item type, add fields, populate, and query end to end.
  </Card>

  <Card title="Connect a source" icon="plug" href="/sections/documentation/databases/ingestion">
    Start syncing from your MDM, IdP, or procurement tool.
  </Card>
</CardGroup>