# Share and review in the studio

Make prototypes, canvases, decks and films with your harness, then review them with pinned comments and share a view-only link.

The **Studio** holds what your harnesses make for people: prototypes, canvases, decks, films, pages, reports and pull request walkthroughs. Each one is an **artifact** with versions, comments, a review and a share link.

Before you start:

- **Studio** is in the left rail when your org has the `studio` module.
- Making things needs a full member, and it runs on your own harness in the [desktop app](/setup/desktop-app). A guest sees only what was shared with them, read only.

## Make something

Open the Studio's **Make something** page.

Pick what to make:

| Kind                           | What it is                                                                                                       |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| Prototype from a description   | Screens and a journey from a prompt or the acceptance criteria, drawn in your design system's tokens             |
| Prototype from the running app | A page from the [built-in browser](/guides/browser-testing), captured as a frame and scanned for private details |
| Walkthrough of a pull request  | A pull request in reading order, with proof, from `/pr`                                                          |
| Deck                           | Slides at 1920 × 1080, with present mode and PDF                                                                 |
| Film                           | A film from a beat sheet or a pull request, with voice, music and sound effects                                  |
| Drawing                        | An illustration or a diagram                                                                                     |

Describe it under **What should it show?**, then choose **Start a session**. A session opens with the right skill and product set. Without a desktop signed in for you, the button says **Open in desktop**.

Ask for what you want. Your assistant publishes it with [`studio_publish`](/reference/mcp-tools#studio-publish), and it lands in the Studio as a draft version.

To change an existing artifact, open it and choose **Work on this**. The new session has the artifact attached.

## Walk what you made

- A **prototype** plays on real device sizes. Its **Device check** card says whether it passed on a device. A check is evidence from one device, and it never decides approval.
- A **canvas** lays out the frames of a product's prototypes, with a lane for each journey. Choose **Arrange** to move frames, then save a draft.
- A **deck** has **Present** and **Export PDF**. The PDF prints on your desktop, or with **No desktop? Print from the browser**.
- A **film** has a **Script** and **Moments**. **Render master** (16:9) and **Render square** (1:1) make a 1080p MP4 on your desktop.

**History** lists every version, and **Compare versions** shows two side by side. **PII report** shows what the check for private details found in a version.

For a live board of frames, stickies and cards that people edit together, see [the design board](/design-system/design-board).

## Comment on it

Choose **Add comment**, then click the spot on the page you mean. **Comment on the whole page** pins nothing.

Write your comment. A comment can be a **Decision**, and a decision can block approval.

**Comments** lists the threads, with filters for _Open_, _Resolved_, _Mine_, _Needs decision_ and _Decisions_. A thread is _Open_, _Addressed_, _Resolved_ or _Won't do_. On a film, a comment sticks to its scene and time.

Your assistant reads the threads with [`studio_threads`](/reference/mcp-tools#studio-threads), fixes the artifact, and answers with [`studio_reply`](/reference/mcp-tools#studio-reply), naming the files it changed.

## Ask for a review and approve

Under **Review**, choose **Request a review**, tick who should look, add a note, and ask them. This needs the Comment role.

Each reviewer answers once on the published version: **Approve &#x76;_&#x4E;_** or **Ask for changes**. The requester is told.

Someone who may approve the artifact chooses **Approve**. Approving pins the published version's hash, so a later draft changes nothing. If blocking comments are still open, **Approve with a reason** records the reason in the audit log. When a workflow's gate checks the design, **Link this task** lets that gate read the approved version. See [workflows, gates and the board](/guides/workflows-and-the-board).

Only a person in the app can request, answer or approve a review. A harness can comment.

## Share it

Choose **Share**. Give people in your org a role:

| Role    | What it allows                                |
| ------- | --------------------------------------------- |
| View    | Open and walk it                              |
| Comment | Pin comments, reply, react, ask for a review  |
| Edit    | Change it, publish, see source                |
| Full    | All of that, plus sharing, links and approval |

**Everyone in** your org gives every member a role, not guests. A guest can have **View** at most.

### Share a view-only link

For someone outside your org, choose **Make a view-only link**. You need Full access and a published version.

- **Expires** runs from 1 to 90 days, and 14 days is the default.
- **Which version**: **Follow the latest that passes** shows each new published version once it passes its check. **Pin to &#x76;_&#x4E;_** keeps the link on one version.
- The link opens with no account. It shows no member names, no comment box and no download.
- **Copy link** works once, when the link is made.
- **Turn off link** stops it for new visitors at once. A page already open stops within 10 minutes.

Some versions need a mark first: one that may show the running app or a repo's work, or one that carries font files. A product maintainer or admin who didn't make it chooses **Mark as safe** and says why. Each new version needs its own mark. A version the private-details check blocked can't have a link until someone reviews it.

> **When the studio is off**
>
> EasyCode staff can switch off the studio with [`studio`](/reference/kill-switches-and-modules#studio). Artifacts can then no longer be opened, published or changed. With [`board`](/reference/kill-switches-and-modules#board) off, live boards open read-only. See [kill switches and modules](/reference/kill-switches-and-modules).
