# Variable License Binding

In some scenarios, you may want to use a different license binding method per customer.

QLM Enterprise's Variable License Binding allows you to associate a binding method with a QLM feature.&#x20;

### Defining Product Features

The first step in configuring Variable License Binding is to define a new feature per license binding method. To do so:

* Launch the QLM Management Console
* Go to the Define Products tab
* Select your product
* For each license binding method that you'd like to support, add a corresponding feature

<figure><img src="https://753808167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyBSbAsJGrr7Cy6XtruH%2Fuploads%2Fn9uTk6b5Kch1uYND05cO%2Fimage.png?alt=media&#x26;token=c4b6d0f2-2f9d-44d8-bb98-f614400d769d" alt=""><figcaption></figcaption></figure>

### Defining the variable license binding

Next, you must associate a different license binding method with each feature.

* Launch the QLM Management Console
* Go to the Protect Your Application tab
* Step to the "Customize Look & Feel / Behavior" page
* Go to the License Properties section
* Set the QlmLicenseBinding property to "PerFeature"
* Click the dropdown box next to QlmLicenseBindingPerFeature and configure the mapping as required
* Complete the wizard and generate the XML/Source code files.
* Update your application to use the newly generated files

<figure><img src="https://753808167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyBSbAsJGrr7Cy6XtruH%2Fuploads%2FlMyKQUZBZVR3LIzZ5REW%2Fimage.png?alt=media&#x26;token=e4bd771a-85a4-4af5-8e3d-3982a6a7c476" alt=""><figcaption></figcaption></figure>

### Creating an Activation Key

When creating an Activation Key for a customer, select the corresponding feature to enforce the required license binding.

<figure><img src="https://753808167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyBSbAsJGrr7Cy6XtruH%2Fuploads%2FvzMOD8DS2ozfdynuahWv%2Fimage.png?alt=media&#x26;token=41ef25cd-2c18-46b2-8b8e-a01da1f161b0" alt=""><figcaption></figcaption></figure>
