> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-5.4/embedding-tellius/embedding-url/embedding-vizpads/edit-save-and-share-a-vizpad.md).

# Edit, save, and share a Vizpad

Learn how to embed Tellius analytics, VizPads, and AI-powered insights into applications with secure and customizable embedded experiences.

### **Editing a Vizpad**

```javascript
telliusFrame.postMessage({
                actionType: "enableEditModeForWindowComm"
            }, "*");
```

The default **Cancel** button will be removed when the above actionType is applied.

### **Saving a Vizpad**

To save a Vizpad to an existing project,

```javascript
telliusFrame.postMessage({
                actionType: "saveVizpadForWindowComm"
            }, "*");
```

{% hint style="warning" %}
When you save the Vizpad using the actionType `saveVizpadForWindowComm`, the Vizpad will not change its state to **View** mode. It will still be retained in the **Edit** mode unless a postMessage is sent requesting to enter **View** mode.
{% endhint %}

On successful saving of a Vizpad, you will be notified with a message in the top banner. In addition, a message with the actionType `VIZPAD_SAVED` will be sent to the embedding app. If a Vizpad is not saved, then the message with the actionType `VIZPAD_SAVED_FAILED` will be sent from Tellius.

### **Sharing a Vizpad**

```javascript
telliusFrame.postMessage({
	"sharedWithId": "ID_of_the_user_to_be_shared",
	"objectId": "ID_of_the_object",
	"objectKind": "vizPad",
	"permission": "w",// it can be ‘w’ or ‘r’
	"sharedWithKind": "user", // it can be ‘user’ or ‘group’
}, "*");
```

* The value of the field `permission` can be set to "w" for write permissions, or to "r" for read-only permissions.
* The value of the field `sharedWithKind` can be "user" or "group" as required.


---

# 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://help.tellius.com/tellius-5.4/embedding-tellius/embedding-url/embedding-vizpads/edit-save-and-share-a-vizpad.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.