---
updatedAt: 2026-08-04T12:15:23.000Z
agentTools:
  projectIndex: https://help.zluri.com/llms.txt
---

# Custom Fields Configuration

Custom fields allow administrators to extend Zluri’s data model by storing additional metadata beyond default attributes. Use custom fields to capture organization-specific information and apply it consistently across entities.

## **Supported Entities**

Zluri supports custom fields for the following entities:

* **Applications**
* **Users**
* **Departments**
* **Vendors**
* **Contracts**
* **Transactions**

<Image src="https://files.readme.io/345a37c1da8cb4cac3342fa79765583f2fcdcf60592396254f248117e2a0f98c-Screenshot_2026-08-04_at_5.08.53_PM.png" alt="Screenshot 2026-01-05 at 4.51.53 PM.png" align="center" />

Each entity maintains its own set of custom fields. Fields apply only within the entity where they are created.

## **Adding a Custom Field**

1. Go to **Settings → Custom Fields**.
2. Select the entity to extend.
3. Click **+ Add New Field**.
4. Select a **Field Type**.
5. Enter a **Field Name**.
6. Configure field-specific options, if applicable.
7. Click **Add Field**.
8. In the confirmation dialog, click **Add Field** again to confirm.

<Image src="https://files.readme.io/953e100a6887408f4201f32b959e7b22a7721c46435b09d3e9840953bd34b322-customfield.gif" alt="Cust.gif" align="center" />

The field becomes available immediately for the selected entity.

## **Field Types**

Zluri supports the following field types:

### **Text Box**

Stores free-form text.

### **Dropdown**

Stores a single value selected from a predefined list.

### **Boolean**

Stores a Yes/No value.
Zluri automatically provides **Yes** and **No** as options.

### **Date Picker**

Stores a date value.

### **Number**

Stores a numeric value, including whole numbers, negative numbers, and decimals.

### **Zluri Entity**

Creates a reference to another Zluri entity (for example, User or Application).

## **Editing and Deleting Custom Fields**

Click an existing custom field to open the edit dialog.
From this dialog, you can:

* Update the **Field Name**
* Delete the field
  Deleting a custom field removes it from all records where it was populated.

## **User attributed data sources**

Zluri supports optional integration mapping **only for User custom fields**.
When editing a **User** custom field, you can connect it to an integration under **Connect this custom field to an integration (Optional)**.
Configuration steps:

1. Open the User custom field.
2. Select an **Integration Name**.
3. Choose **Schema Key** or **Function** as the mapping type.
4. Select the corresponding **Field Name** from the integration.
5. Review the **Sample JSON Data** to confirm the mapped value.
6. Click **Edit Changes**.
7. In the confirmation dialog, click **Save Changes** to confirm.
   When configured, Zluri syncs the custom field value from the mapped integration attribute after the next sync.
   This option does **not** appear for Applications, Contracts, Vendors, Departments, or Transactions.&#x20;

   ![](https://files.readme.io/045eb71c3d4b7efcb360a6811db6e07473254032c1a820c69fc684078a217f9a-Screenshot_2026-08-04_at_5.44.08_PM.png)

## **Where Custom Fields Appear**

After creation, custom fields appear across the platform:

* As columns in list views
* As filters in tables
* In exports
* In workflows as conditions and variables
* In dashboards and insights, where applicable

Custom fields follow the visibility and access rules of their parent entity.