> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/account-settings/properties/customize-properties.md).

# How to customize properties?

Customizing properties will enable you to gather and store the right information on Leads, Deals, Contacts, Transactions, Customers, Partners, Rewards, and Products.

## Adding Custom Properties <a href="#adding-custom-properties" id="adding-custom-properties"></a>

To change properties here are the following steps:

* Go in **Account Settings** > **Properties** (top right corner menu)
* Select the object you want to edit (Leads, Deals, Contacts, Transactions, Customers, Partners, Rewards, Products)
* Click the Add button on the object you want a new property to:

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-4b8b9c0ebad11fe369608a462387fba0b95d1201%2F6151d8a112c07c18afdd7ede.png?alt=media)

## Property Configuration

Here are a few things that are important in property configuration:

1. You must understand to use the right type for the right property. Properties need to have the right type to ensure data integrity (ex: to collect emails, dates, or list of values).
2. Choose if the property is required or not. You must check this option to ensure partners will provide the mandatory information, and keep the data in the PRM clean

In order to customize properties please see the video below:

{% embed url="<https://www.loom.com/share/c54358bb95a94a44b01848c18ef9cf21>" %}

{% hint style="info" %}
**Property Visibility**

please see this article about: [How to change properties visibility for partners?](/account-settings/properties/change-properties-visibility.md)
{% endhint %}

## Reordering Properties

The order in which they are shown on the properties tab is the order in which they will be displayed on the forms/tabs/pop-ups. It is important to reorder your properties in order to reflect your processes.

Here is a short video showing how to reorder your properties, please ensure you save the changes you have made:

{% embed url="<https://www.loom.com/share/f1fc3bb6753b4fb3b18f01927f36d99b>" %}

## Removing Properties

You have the ability to remove a property. If you remove a property, the data stored in all objects (leads, deals, etc.) containing this property won't be erased! Removing a property won't erase data (for example: if you request the leads, deals, etc via API you will still see the values stored).

Here is how to remove a property, please ensure you save the changes you have made:

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-161cf8d6de15dd36b609046d9218b3e7cb638903%2F617c0afbefc78d0553e54fbf.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs-vnext.kiflo.com/account-settings/properties/customize-properties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
