# Elastic Access Concepts Relevant Only for FlexNet Operations Users

In addition to the concepts described in [Elastic Access Concepts for All Back-Office Types](/guides/elastic-access-concepts-for-all-back-office-types), producers who use FlexNet Operations as their back office need to be aware of the following terms. These differ from the concepts that producers are already familiar with in the context of FlexNet Operations:

- [Token Structure When Using FlexNet Operations](#token-structure-when-using-flexnet-operations)
- [Elastic Access License Model](#elastic-access-license-model)
- [Elastic Access Line Item](#elastic-access-line-item)


## Token Structure When Using FlexNet Operations

This section complements the information described in section Tokens.

A token is not a built-in concept in FlexNet Operations. Therefore, it must be represented in FlexNet Operations using a compound structure with three parts: a product with a single feature, and a dedicated license model.

The product must contain a feature for historical reasons. The feature as such does not provide any functionality in the context of Elastic Access.

Producers create:

- a license model of type “Dynamic Monetization | Elastic Access”,
- a product (which, for clarity, could simply be named “Elastic Token”),
- a feature (which, for clarity, could also be named “Elastic Token”),


and then add the feature to the product and associate the license model.

The following diagram depicts the token structure:

![token structure](/assets/pas_tokenstructure.19a3f866ba8b43e71311a6683aa5279921516d0a7d383c1946ea79699f8ee9a7.9bb1daa4.png)

A token is modeled by defining a product and giving it a single feature and associating it with a license model.

The name "Elastic Token" is suggested here for clarity of illustration. You may call the product/feature combination anything you like, according to your own preference.

For step-by-step instructions about creating an entitlement line item for tokens, see section [Preparing Your Dynamic Monetization Instance: Information for Producers Using FlexNet Operations](/tutorials/preparing-your-dynamic-monetization-instance-fno).

## Elastic Access License Model

Producers must create a specific license model for Elastic Access (using the license model type "Dynamic Monetization | Elastic Access") to be able to create tokens. This license model must be used when creating line items for tokens, because only line items created with such a license model will be mapped to an Elastic Access instance.

The Elastic Access license model is a metered consumptive model: once the tokens in a line item are exhausted, new tokens must be sold to the end customer.

Line items created with the license model type "Dynamic Monetization" may not be mapped to any other service, such as FlexNet Embedded license servers or devices, because they will be automatically mapped to Dynamic Monetization.

License models for line items containing tokens must also set the attribute `elastic` to `true`.

For step-by-step instructions for creating a sample Elastic Access license model, see [Exercise 1: Creating a License Model](/tutorials/preparing-your-dynamic-monetization-instance-fno#exercise-1.-creating-a-license-model).

## Elastic Access Line Item

This topic defines an Elastic Access line item for users of FlexNet Operations. The term *“Elastic Access”* line item is used to emphasize that it differs from the line item concept that users are familiar with from FlexNet Operations, as described below. In the remainder of this document, the terms “Elastic Access line item” and “line item” are interchangeable. Both refer to line items that can be mapped to an Elastic Access instance.

An Elastic Access line item captures an entitlement to a number of tokens which have been sold to an end customer, and which will be made available through an Elastic Access instance. It requires the product-feature-license model structure described in section [Tokens](/guides/elastic-access-concepts-for-all-back-office-types#tokens).

- An Elastic Access line item will be automatically mapped to an Elastic Access instance accessible to the end customer (only one instance may be used for an end customer—if a customer has multiple line items for Elastic tokens, these will all be mapped to the same instance).
- An Elastic Access line item may not be mapped to any other license server (such as a FlexNet Embedded Cloud License Server or local license server).