---
title: "Table Concepts"
canonical: "https://help.agiloft.com/space/A2508SD/134054074/Table+Concepts"
format: markdown
---
In Agiloft, contract details, approval workflows, documents, and related data are all stored in interconnected tables. Tables define the attributes of your data and stores that data in records in the database. Tables include the set of fields, relationships, rules, and conditions that govern how records act in the system. Data from one table is displayed in other tables through linked fields in one-to-one, one-to-many, and many-to-many relationships.

This article introduces you to table concepts and describes the standard fields that are common to all tables.

# Table Types

There are two types of tables in Agiloft: background tables and process tables.

### Background Tables

Background tables function as repositories of records. They primarily hold the static data that is used to support processes, in process tables, and contain little to no associated workflows or automation. Background tables store basic information about people, places, and organizations. Although data in background tables isn't typically changed by processes or workflows, it is still created and often updated by power users.

> ℹ️ **Example**
> ℹ️ 
> ℹ️ A good example of a background table that appears by default in the out-of-the-box system is the People table. Records in the People table represent employees or external users and aren't consistently being updated from the results of a workflow, like Contract and Task records are. Like most background tables, People data remains relatively static but can be updated manually when necessary, for example, when an employee's role changes or they change their last name.

### Process Tables

Unlike background tables that generally hold static data, process tables store records that are actively worked on by following a workflow or other dynamic activity. Process tables generally pull in records and field values from background tables, such as when Contract records pull in data about companies and people.

> ℹ️ **Example**
> ℹ️ 
> ℹ️ The most prominent example of a process table is the Contracts table. The process of creating and managing Contract records has several stages, and extensive workflows and automation are employed to move contracts through their lifecycle. The Sourcing Events table is similar to Contracts in that workflows and automation help manage the lifecycle of Sourcing Event records.

# Table Groups

In the out-of-the-box system, tables are grouped by platform module or functional area. For example, tables related to managing contract lifecycles are grouped under Contract Management, and tables related to managing document and email templates are grouped under Template Management. Some process tables, like Approvals and Tasks, and supporting tables, like Attachments, are shared between table groupings.

> ℹ️ The groupings and tables users see are determined by which navigation menu is the default menu for their primary team. This guide focuses on the out-of-the-box Admin Navigation Menu. You can view and customize the groupings in the navigation menu and the tables within groups for all teams by going to **Setup > Look and Feel > Navigation Menu Setup**. For details, see [Navigation Menu Setup](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714797) in the Help Guide.

- [Contract Management](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134055270): Tables that support contract lifecycle management
- [Supplier Sourcing Management](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134058040): Tables that support sourcing event and supplier information management
- [Shared Tables](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134058528): Tables that are designed to support multiple functional areas of the system
- [Template Management](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134058583): Tables that support contract lifecycle and supplier sourcing management processes
- [AI Platform Management](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134059835): Tables that support out-of-the-box and add-on AI features
- [System Admin](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134060033): Tables that are system-managed, like Activity Log and Communications, as well as tables that manage other automation and functions
- [Data Admin](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134060474): Tables that store relatively static reference data used throughout the system, such as company, country, state, and currency data
- [Hidden Tables](https://agiloft-public.atlassian.net/wiki/spaces/A2508SD/pages/134061285): Tables that are hidden from the Admin Navigation Menu by default because they aren't accessed directly but may be linked to other tables or dashboards

# > Macro (anchor)

Standard Fields

All tables in the out-of-the-box system include the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Communications | Communications Search Result | Used to display the emails related to records in the table. This field performs the following search to find records in the Communications table that are linked to the record that includes the Communications field.<br>`Linked ID = recordid() AND Linked ID = tableid()` |
| Created By  
Creator Login  
Creator Team | Link to selected fields from other table: People | These linked fields show the full name, login, and primary team values of the user who created the record. |
| Date Created | Date/Time | Lists the date and time the record was created, according to the KB time. |
| Date Updated | Date/Time | Lists the date and time the record was last updated, according to the KB time. |
| Deletable | Choice:<br>- Yes
- No | Controls whether the record can be deleted. The field defaults to Yes and can be changed to No for specific records to prevent them from being deleted. |
| Demo Data | Choice:<br>- Yes
- No | This field can be used to tag records that include data for demonstrative purposes only and should be deleted when the system is ready for production. Records that include this field and have a value of Yes can be removed in bulk by Agiloft Support or Professional Services. |
| History | History | In order to maintain a history of changes to records, this field creates timestamped entries that log changes made to records in the table. It's a critical resource for storing data that is used by reports and rules and should never be deleted. For more information, see [History Fields](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43716066) in the Help Guide. |
| ID | Auto-Increment | The unique identifier for each record in the table. |
| Type | Type of the SW object | Defines the type of record, such as a Sourcing Event or Contract record. |
| Updated By  
Updater Login  
Updater Team | Link to selected fields from other table: People | These linked fields show the full name, login, and primary team values of the last user who updated the record. |