> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/widgets-dashboard.md).

# Widgets dashboard

Find mobile and web widget designs on the widgets dashboard or create one from a template or blank canvas.

### Choose a starting point

Open **Mobile In-App → Widget → Design Widget** or **Web Tools → Widget → Design Widget**.

The dashboard lists every widget available for the selected channel. Use it to find existing designs or create a new one.

Each row shows:

* **Name** is the internal widget name.
* **Type** is the widget format or source.
* **Description** is the internal purpose of the widget.
* **Created** and **Updated** is when the widget was created or last changed.
* **Updated by** is the teammate who last modified it.

Use clear names and descriptions. They make campaign selection and maintenance safer.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FtPqgJqQ90vIdy3addWUC%2FEkran%20Resmi%202026-08-13%2010.58.08.png?alt=media&amp;token=bd9784e4-94d9-401e-9205-0698a18454cb" alt=""><figcaption></figcaption></figure>

### Manage saved widgets

Use **Search** to find a widget by name. This is useful when your workspace contains many templates, drafts, or campaign variations.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FWi7WzBIPXeTyQ6XCflB3%2FEkran%20Resmi%202026-08-13%2011.01.17.png?alt=media&amp;token=2fc51bf5-b2d1-4087-84ed-3f6a232107e3" alt=""><figcaption></figcaption></figure>

Open the actions menu for a saved widget to manage it:

* **Copy link** copies a direct link to the widget.
* **View widget** opens the saved design for review.
* **Edit** changes the layout, content, or settings.
* **Duplicate** creates an independent copy.
* **Delete** removes an unused widget.

Duplicate a widget before adapting a successful campaign. This preserves the original design and separates campaign variations.

Delete only unused designs. Confirm that no active campaign still uses the widget.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FXKPCCph8EcE7larpdSBU%2FEkran%20Resmi%202026-08-13%2011.01.49.png?alt=media&amp;token=5a69a6c4-a570-4b8e-b7cc-bf766cfa21eb" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F1eE9IlgQSHxOaJlqvGf2%2FEkran%20Resmi%202026-08-13%2011.00.55.png?alt=media&amp;token=5a3f1142-f4b6-43f8-9e92-77844a2fb2f7" alt=""><figcaption></figcaption></figure>

### Create new widget

Click **New Widget** to start a design. Add a name and description for internal use.

Choose **Blank Widget** when you need a custom layout. Start with one campaign goal, then add the required views and elements.

Choose a ready-to-use template from **Widget Gallery** when its structure matches your use case. You can update the text, styling, elements, and actions after selecting it.

Use a template as a starting point, not a restriction. Review every element and action before publishing.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FxrQ4qpErXf1zuuc9TUKx%2FEkran%20Resmi%202026-08-13%2011.03.38.png?alt=media&amp;token=04544242-a1f4-4ed8-95d0-d898f21c1751" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FSF5rOXyTDlLdyFKbGx1o%2FEkran%20Resmi%202026-08-13%2011.04.46.png?alt=media&amp;token=d83a0dc5-af17-4fc1-a589-f1c7d9e4a2b3" alt=""><figcaption></figcaption></figure>

### Design and add behavior

Configure the widget settings before detailed design. Then build the layout and define its behavior.

1. [Configure widget settings](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-settings.md)
2. [Design widget layout](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/design-widget-layout.md)
3. [Configure widget actions and validation](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-actions-and-validation.md)

Give interactive elements clear identifiers before assigning actions. Preview every view before publishing.

{% hint style="info" %}
After building your widget, continue to **Publish and target**.
{% endhint %}


---

# 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://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/widgets-dashboard.md?ask=<question>&goal=<user_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.