> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/developers/no-code-saas-example/creating-a-product-and-entitlement.md).
# Creating a Product and Entitlement
Create a test product, features, offering, entitlement, and activation codes in the Zentitle2 UI to match the SaaS demo app.
### Creating a Product and Entitlement in the Zentitle UI for testing
To make the demo work, you will need to add a new entitlement with the right features and attributes to match those in the demo app.
{% hint style="info" %}
First, [read the documentation](/zentitle2-docs/ui-product-catalog/licensing-and-business-models.md) and fully understand the product paradigm and how to set up a product and its parts, including an entitlement, with activation codes.
{% endhint %}
**Once you are familiar with how Zentitle2 works, you can set up the specific parameters required to run the demo successfully—all these changes are necessary to allow you to test successfully.**
### Steps to match the server side with the demo app:
 Login to your account and navigate to the "product" section.
 Add a new product. Name it something useful, in this case, "SaasDemoApp".
 Now click the "features" tab and start adding the test features, attributes, and advanced features for testing.
* Add features with the following keys:
* **Calendar,**
* **ProjectPlanning,**
* **Collaboration,**
* **Reporting,**
* **ReportingAdvanced,**
* **Security.**
* Set the "value" to **Enabled** for them all.
* Click Save, and repeat.
* Repeat until all the demo features have been added and saved.
***
 Next, Add two **string** attributes with the following keys:
* **CompanyName,**
* **PlanName.**
* Click Save, and repeat.
***
 Next, Add three **"advanced features".**
* First, a **usage counter** with the key: **CT1.** Set the value to **100** (conversions) and click save.
* Next, Add an element pool with key: **EP1.** Set the value to 2 and click save.
* Next, Add a floating feature with key: **FF1.** Set the value to 20 and click save.
When you are done the features page should be completed with the demo components required to test.
***
### Offerings
The next tab is editions. We will skip that tab as we will use the default edition (no need to edit the edition part) so go to the next tab, "Offerings".
 Add an offering by clicking on the add button on the top right. The Product is pre-selected.
Edit the offering parameters exactly as below:
* Give the offering a name e.g. Standard
* Add in a short dummy SKU
* Leave the edition as default
* Pick a plan from the existing examples (e.g., a one-year subscription with **activation**).
* Set the seat count e.g. 1
* Set the mode e.g. concurrent
* Click Save
***
### Entitlements
 Now to the final couple of steps. Add an **entitlement** and edit the parameters.
* Navigate to the "entitlements" option in the left navigation or **the last tab when editing a product.**
* Click Add Entitlement
* If you start in the product section the offering name is pre-selected but you can change it from the drop-down menu**. If you start in the offering section the offering name is fixed and pre-selected.**
* Skip the customer (unless you added a test one already etc and want to try that)
* Add order ref as you wish
* Click save
 Now we **edit** the entitlement to add in some test parameters under the "attributes" fields we added earlier.
* Fill in the company and plan attribute to your test values, e.g., "Boeing" for the company name and "Standard" for the plan name for example.
* The rest of the parameters should be prefilled.
* Click save.
***
### Activation codes
 The final serverside step is to Add activation codes to the entitlement (e.g., add ten codes for testing).
* Go to the bottom of the new entitlement page
On the bottom right is the activation codes section.
{% hint style="warning" %}
This activation code area has moved to a separate tab, and this doc will be updated soon!
[See the activation codes area for update details.](/zentitle2-docs/ui-entitlements/working-with-entitlements/activations.md)
{% endhint %}
* Click add.
* Next, click Generate
* Add 10 (or whatever number of codes you like)
* Click Save
* Now, you will see your codes ready to use in the codes section.
* You can copy a code to the clipboard and paste it into the SaasDemoApp on your desktop or export the codes for testing later.
**You are now all set to move to the SaaS demo (run as a desktop app), keep the Zentitle UI open as well so you can see what happens on the server when you perform actions on the desktop client.**
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nalpeiron.com/zentitle2-docs/developers/no-code-saas-example/creating-a-product-and-entitlement.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
