> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ideatura.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Viewers and markup

> Inspect references beside the conversation, capture views and add markup.

<h2 id="side-panels">
  1\. Side panels
</h2>

<span id="side-panels-overview" />

<span id="side-panels-in-ideatura" />

<span id="side-panels-check-the-result" />

The split-panel control opens a viewer beside the main Studio area. File tabs, close controls and the panel boundary organise the workspace.

Opening or closing a preview is separate from saving or deleting its underlying file. Keep the source visible while discussing a change.

An image attachment can also open as a preview over the conversation. Click the attachment to inspect it, then close the preview with **X**.

<img src="https://mintcdn.com/ideatura/es2pEmCgfCrT5MoG/images/studio-tour/reference-preview.svg?fit=max&auto=format&n=es2pEmCgfCrT5MoG&q=85&s=223191d027b49a5bda54742247405751" className="w-full h-auto mx-auto" alt="Image attachment preview over the conversation: 1 image; 2 close preview. This example does not show the side-panel controls." width="1449" height="1001" data-path="images/studio-tour/reference-preview.svg" />

<h2 id="capture-a-view">
  2\. Capture a view
</h2>

<span id="capture-a-view-overview" />

<span id="capture-a-view-in-ideatura" />

<span id="capture-a-view-check-the-result" />

The empty capture panel asks you to select an app to capture and annotate. Choose the intended application and document before taking a visual reference.

A captured image supplies visual context. Application access determines what Ideatura can read or change in the underlying document.

<h2 id="add-markup">
  3\. Add markup
</h2>

<span id="add-markup-overview" />

<span id="add-markup-in-ideatura" />

<span id="add-markup-check-the-result" />

Choose the pen, shape or text tool in the viewer toolbar. Mark a specific part of the image or model view and state the intended change in words.

A markup communicates intent; it does not independently establish exact dimensions or confirm a native edit. Include the dimensions, element scope and exceptions the drawing cannot express.

<h2 id="edit-markup">
  4\. Edit markup
</h2>

<span id="edit-markup-overview" />

<span id="edit-markup-in-ideatura" />

<span id="edit-markup-check-the-result" />

Use selection and eraser controls to correct an annotation. Undo and redo change markup history; the clear/delete control removes marks according to its current scope.

Distinguish changing the annotation from changing the IFC or connected application model. Review the marked image before submitting it.

<h2 id="viewer-actions">
  5\. Viewer actions
</h2>

<span id="viewer-actions-overview" />

<span id="viewer-actions-in-ideatura" />

<span id="viewer-actions-check-the-result" />

The viewer menu provides **Attach**, **Pin** and **Clone** actions. Check the conversation and file location, then choose whether to add material to a message, pin context or create an editable copy. Confirm the attachment, pinned state or Workbench copy afterward.

<h2 id="save-viewer-files">
  6\. Save viewer files
</h2>

<span id="save-viewer-files-overview" />

<span id="save-viewer-files-in-ideatura" />

<span id="save-viewer-files-check-the-result" />

The IFC panel shows history, download, save and close controls above the file. These operations have different destinations and scopes.

Check whether you are saving an editable Studio copy, downloading a file or saving a connected application document. Reopen the intended output to confirm the result.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.