# Using Custom License Fields

**URL:** <https://community.replicated.com/t/using-custom-license-fields/20>\
**Category:** Packaging an application\
**Created:** [March 6, 2018, 7:18pm UTC](https://community.replicated.com/t/using-custom-license-fields/20 "2018-03-06T19:18:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/marc/32/7_2.png) [@marc](https://community.replicated.com/u/marc)\
**Post date:** [March 6, 2018, 7:18pm UTC](https://community.replicated.com/t/using-custom-license-fields/20/1 "2018-03-06T19:18:23Z")

</div>

**Note** : For the latest documentation, please see [Managing Custom License Fields](https://docs.replicated.com/vendor/licenses-adding-custom-fields) in the Replicated product documentation.

The previous answer is reproduced below for posterity.

* * *

Custom license fields are key value pairs that can be created in the vendor portal, securely delivered to each on-prem instance and kept in sync through automated update checks. This is useful if specific application level information might change from customer to customer.

Examples of custom license fields are “seats” to limit the number of active users or “hostname” in order to specify the domain that the application can be run on.

## Creating Custom License Fields

Custom license fields are generally created and managed from the [License Fields section](https://vendor.replicated.com/license-fields) of the vendor portal. Any new `Required` field will need to be set for all existing Customers (either with custom data or by using the `Default` value) as well as all future Customers. Fields that are marked as `Hidden` will not be displayed on the :8800/license page of the on-prem admin console. `Title` will be the name that is displayed on the :8800/license page of the on-prem console. `Field` is the unique id. `Type` is either an ‘integer’, ‘string’ or ‘text’ type.

## Setting Custom License Fields

The values can then be set for each Customer in the manage customer screen of the [vendor portal](https://vendor.replicated.com/customers) in the same way that standard customer fields are managed.

## Accessing the Field Values

These values are available in the on-prem instance and can be used to configure or alter the application. During configuration, these fields can be read from the [template functions](https://help.replicated.com/docs/kubernetes/packaging-an-application/template-functions#licensefieldvalue) and then used to overwrite config files or be injected as environment variables. Once the application is running, these values are synced automatically on the update check interval. Changes can be detected in the running instance by polling the [Licensing Integration API](https://replicated.readme.io/docs/license-api).

These fields are cryptographically signed by Replicated using PKI and the Replicated components will not install or update the license fields if the data does not match the signature.

---

<div class="post-metadata">

**Author:** ![Ken\_Mayer](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/ken_mayer/32/315_2.png) [@Ken\_Mayer](https://community.replicated.com/u/Ken_Mayer)\
**Post date:** [September 28, 2018, 11:48pm UTC](https://community.replicated.com/t/using-custom-license-fields/20/2 "2018-09-28T23:48:04Z")

</div>

Is there a way to remove or modify a custom license field so that I can change its type? I fat fingered a field and made it a text instead of string field.

---

<div class="post-metadata">

**Author:** ![areed](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/areed/32/12_2.png) [@areed](https://community.replicated.com/u/areed)\
**Post date:** [February 26, 2020, 10:47pm UTC](https://community.replicated.com/t/using-custom-license-fields/20/3 "2020-02-26T22:47:51Z")

</div>

You can’t delete a license field in the vendor portal but you can with an API call with native, Swarm, and AKA apps: `DELETE https://api.replicated.com/vendor/v1/app/:appId/licensefield/:licenseFieldName`. This can affect existing customer installs.

---

<div class="post-metadata">

**Author:** ![grant](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/grant/32/9_2.png) [@grant](https://community.replicated.com/u/grant)\
**Post date:** [February 25, 2022, 9:18pm UTC](https://community.replicated.com/t/using-custom-license-fields/20/4 "2022-02-25T21:18:36Z")

</div>

You can now delete custom license fields for KOTS apps: [Using and Creating Entitlements - Kots.io](https://kots.io/vendor/entitlements/creating-entitlements/#deleting-entitlement-license-fields)

---

<div class="post-metadata">

**Author:** ![Jonquil\_Williams](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/jonquil_williams/32/590_2.png) [@Jonquil\_Williams](https://community.replicated.com/u/Jonquil_Williams)\
**Post date:** [January 3, 2023, 10:31pm UTC](https://community.replicated.com/t/using-custom-license-fields/20/5 "2023-01-03T22:31:28Z")

</div>

For the latest documentation, please see [Managing Custom License Fields](https://docs.replicated.com/vendor/licenses-adding-custom-fields) in the Replicated product documentation.
