--- title: "Recipe List" slug: "recipe-list-widget" updated: 2026-07-29T07:48:01Z published: 2026-07-29T07:48:01Z canonical: "learn.servitly.com/recipe-list-widget" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Recipe List The widget allowing the user to manage recipes, shares recipes and send them to the connected machines. ![Recipe List](https://components-manager.servitly.com/components/RecipeList_1/IMAGES/_screenshot?owner=AG_Servitly) The widget displays all the [*Recipes*](https://help.servitly.com/hc/en-us/articles/10854999105693) available to the Thing, including the ones directly saved on the Thing and the those which are made available from the Thing Definition. The *Add Recipe* button allows the creation of a new Recipe, instead, by clicking on the three dots icon it is possible to edit a Recipe, or in alternative import/export a recipe through a CSV file. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(532).png) By clicking the Edit button, you can edit a recipe. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(533).png) A recipe is described by the following properties: - **Name**: the recipe name displayed within the list. - **Description**: the recipe description providing basic recipe information. - **Shared**: if YES the recipe is visible to all the Thing (same Thing Definition) of the Customer, else is visible only to this Thing. The *Edit parameters* link opens the list of parameters and values associated with the edited recipe. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(534).png) It is also possible to include more parameters into the recipe by selecting them from the list of all parameters. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(535).png) The Recipe List widget can also be placed on a top-level page (e.g. Overview), allowing, for instance, a customer to edits its recipes. Recipes edited outside a specific thing will be automatically shared with all customer's things. In this case, the creation of anew recipe will require the user to select the target thing-definition. ### Template Syntax Below you can find some examples of how to use the component within a template. ```xml                     ``` ## Component Reference Here is a comprehensive list of all the elements and properties that can be used to configure the component. #### Recipe List `<recipe-list-widget>` | *Title* | The title displayed on the top part of the widget box. **Name**: title **Type**: STRING \| Optional `[title]="'Recipes'"` | | --- | --- | | **Rendering** | | *Availability* | Configure availability based on active features on Digital Plan on Add-ons **Name**: hasFeature **Type**: FEATURE (multiple) \| Optional `[hasFeature]="['feature_a', 'feature_b']"` | | *CSS Class* | The name(s) of the CSS class used to customize the widget layout. **Name**: class **Type**: STRING \| Optional `class="my-custom-class"` | | *Visibility Condition* | The expression that allows you to reduce the visibility of the element. **Name**: *ngIf **Type**: STRING \| Optional `*ngIf="getUser().organizationId != null"` | ## Full Syntax Example ```xml ```