> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/organize-your-data/duplicate-widgets.md).

# Duplicate widgets

Because sometimes you want the same report across a multitude of dashboards. 

Not to fret, CorralData has *two* different ways for you to do this! Inside the widget menu you'll see *<mark style="color:purple;">**Duplicate to**</mark>* as well as *<mark style="color:purple;">**Create Linked Copy**</mark>***:**

<figure><img src="/files/hd8jovEyJJ0qVN2mMpaW" alt=""><figcaption></figcaption></figure>

So, what's the difference?

*<mark style="color:purple;">**Duplicate to**</mark>* creates a standalone copy of the selected widget to the selected dashboard. The two widgets have no ties back to one another after the creation and you can make changes to either widget without affecting the other.&#x20;

*<mark style="color:purple;">**Created linked copy**</mark>*, on the other hand, creates a *linked* copy of the selected widget to the selected dashboard so that any changes made to one widget affects all of its linked copies no matter the dashboard.&#x20;

So which do you choose?

If you want to use a specific widget on another dashboard as a base for a new report (ie. you anticipate making changes to this widget specific to its new dashboard) then select *<mark style="color:purple;">**Duplicate to**</mark>.*

If you want to see the same exact report across multiple dashboards with consistency and accounting for any future changes, then select *<mark style="color:purple;">**Create linked copy**</mark>**.***

{% hint style="info" %}
If you're having trouble and require technical assistance, feel free to reach out to <support@corraldata.com>.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.corraldata.com/kb/organize-your-data/duplicate-widgets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.