# Lookups

## About lookups

In the Tuum system, the lookups hold lists of enum values with their language-based explanations (translations). You can use them as default values present in the Tuum system or modify them to fit your custom needs.

**For example,** the list of valid customer documents is ID card, passport, and driver’s licence. Whenever a new customer document is entered, the Tuum system validates the entry against this list. You can remove some of the items like ID card from the list and amend the list with a new item like living permit, to make the list more relevant for your use case. After these changes, all the subsequent entries are validated against the updated list. Additionally, if you use that list in your graphical user interfaces for selection options in drop-downs, the updated list will be displayed there.

## Definitions

* **Lookup group -** The domain or module that uses the lookup. These values are pre-defined and cannot be edited. The groups you see depend on your subscription.\
  For example, **ACCOUNT**, **LOAN**, **CARD**, **EXTERNAL**, etc.
* **Entity -** Reference to the object of a group that the lookup is related to.\
  For example, **LOAN.APPLICATION** - refers to the application object in the loan module.
* **Lookup type code -** The code for the lookup type itself. It describes a property of the entity.\
  For example, a lookup type code called **STATUS** in the entity **LOAN.APPLICATION** and the lookup group **LOAN**.
* **Lookup code -** Values for the lookup type code.\
  For example, lookup codes with values **CREATED** and **PROCESSED** for the **STATUS** lookup type code.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tuum.com/backoffice-user-guides/iDyT31cW9CYApPltrXUd/administration/lookups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.