> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/build/interactive-demo/edit.md).

# Edit

Once you've recorded your Arcade, you can start editing: add and remove steps, add context, trim video, highlight features, and more.

## Basics

### How can I undo an edit?

There's no undo button in the toolbar, but you can press `⌘Z` (`Ctrl+Z` on Windows) to undo recent edits and step back through your changes.

***

## Collaborate

{% hint style="info" %}
You need to be on the Growth plan to collaborate on Arcades.
{% endhint %}

### Can I view my teammate's Arcades?

Yes! If an Arcade is placed in a shared workspace, all teammates can:

* View the Arcade
* Share or embed using the share link

## Can I edit my teammate's Arcade?

Usually, yes. Arcades belong to the workspace, not to the person who created them. Whether you can edit one depends on two things: your role in that workspace, and whether that specific Arcade has been shared with you.

### The short answer

* Editor, Admin, or Owner — you can edit any Arcade in the workspace, including ones your teammates created.
* Viewer or Billing User — you can view Arcades but not edit them.
* Anyone can be invited to edit one specific Arcade, even if their role wouldn't normally allow editing.

### What each role can do

| Role         | Editing Arcades                         |
| ------------ | --------------------------------------- |
| Owner        | Edit any Arcade in the workspace        |
| Admin        | Edit any Arcade in the workspace        |
| Editor       | Edit and share Arcades directly         |
| Collaborator | Edit Arcades; sharing requires approval |
| Viewer       | View only — no editing                  |
| Billing User | View and manage billing — no editing    |

If you open a teammate's Arcade and the editing tools aren't available, your role is almost always the reason.

### Sharing edit access to a single Arcade

You don't have to change someone's role to let them work on one Arcade. An admin can share a specific Arcade with a person and set their access to View or Edit.

A few things to know:

* Edit access can be granted to a teammate whose workspace role is Viewer. When that happens, their workspace role is upgraded to Editor.
* Access is granted per person, per Arcade, so it doesn't affect anything else in the workspace.
* Inviting workspace members to edit a specific Arcade is available on Growth and above.
* Inviting people outside your workspace to edit is available on Enterprise.

### If you can't edit an Arcade you need

1. Check your role under Settings → Team. If you're a Viewer or Billing User, that's the block.
2. Ask an Owner or Admin to either change your role, or share that one Arcade with you and set your access to Edit.
3. If you only need to build on top of the Arcade rather than change the original, duplicating it gives you your own copy to edit. (Duplicating also requires an edit-level role.)

### A note on ownership

The person who created an Arcade is recorded as its creator, but that doesn't make it private to them. Every Arcade lives in the workspace it was made in, and access follows the workspace — so a teammate leaving or changing roles doesn't strand their Arcades.

{% @arcade/embed url="<https://app.arcade.software/share/ZR0fUykvxXAV1ykk4UaK>" flowId="ZR0fUykvxXAV1ykk4UaK" %}


---

# 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.arcade.software/kb/build/interactive-demo/edit.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.