Overview of Entitlements
An Entitlement in FlexNet Operations LLM is a representation of which software deliverables should be granted to which Account. The Entitlement includes the Catalog Item and the duration of time for which access to it should last. It can also be referred to as an order. The following represents the work flow pertaining to Entitlement in FlexNet Operations LLM:
Entitlement Workflow in FlexNet Operations
Account Concepts
Accounts are customers who you sell to or are licensed to access the product.
| • | Examples include companies, sites, departments or divisions. |
| • | Accounts are entitled to software, and all Members associated with an account have the same access. |
| • | An Account needs to have one or more Members associated with it. |
| • | At least one Member must exist in order for someone at the company to have access the site. |
Member Concepts
Members are end users.
| • | A Member’s e-mail address is their username, and FlexNet Operations LLM generates a password. Username and password are sent via the Welcome Email. |
| • | Software access for a Member is controlled by which Account they are on. |
| • | The Member’s physical address is used for export compliance. |
Entitlement Concepts
Frequently, Entitlements are order driven. Entitlements can also be thought of as a way of grouping Line Items.
Entitlement header information shows up on the Order History page, and can be sent in an Order Notification email.
Line Item Concepts
Line Items specify the Catalog Item to grant an Account access to.
| • | Line Items have Effective and Expiration dates and typically map to maintenance contracts. |
| • | The end user view of specific Product versions is determined by how Line Item dates overlap with Product effective dates that are associated with the entitled Catalog Item. |