---
title: "Lookup"
description: "Understanding Lookup Column!"
---

### Example organization structure

Consider an organization with
- 5 departments (company departments), each department has a team name & associated team code. Each `Team` **has many** `Employees` - relationship has been defined using `LinkToAnotherRecord` or `Links`column
- 5 employees working at different departments

![company-employee-table](https://github.com/nocodb/nocodb/assets/86527202/cbfb6278-9016-4913-b3c0-4a6549c660ac)

<!-- ![Screenshot 2022-09-09 at 12 18 40 PM](https://user-images.githubusercontent.com/86527202/189291758-21c81ec6-7967-45f1-b49c-b3b6f2701edc.png) -->
<!-- ![Screenshot 2022-09-09 at 12 19 16 PM](https://user-images.githubusercontent.com/86527202/189291766-f619078e-0881-4531-a3f8-ede22269f6fc.png) -->


Now, let's explore procedure to retrieve team-code information in Employee table using **LOOKUP** columns

### Configuring a lookup column
- Add new column : Click on '+' icon to the left of column headers in Employee table
- Feed column name
- Select column type as 'Lookup'
- Choose child table
- Select child column
- Click on 'Save'

![lookup create](https://github.com/nocodb/nocodb/assets/86527202/45f2757e-9cc5-4eff-903d-d59ad812abb0)


Required information is now populated in the newly created column

![lookup display](https://github.com/nocodb/nocodb/assets/86527202/586fffab-0dfa-4eef-97ec-521495f4979b)


## Additional notes
- Nested 'Lookup' supported: a Lookup field can have its child column datatype as Lookup (or Rollup).