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

# Sofia notebooks

> Create, edit, present, schedule, and share analysis notebooks and slide decks with Sofia.

Sofia notebooks give you an editable document and presentation canvas grounded in your workspace's simulations, uploaded conversations, runs, and metrics. Start from a blank notebook or ask Sofia to draft an analysis, executive readout, or slide deck, then refine the document directly or through the docked Sofia sidebar.

## What you can build with notebooks

Unlike a fixed report template, a notebook lets you combine narrative prose, charts, multi-column layouts, illustrations, animated GIFs, video, and clickable links to the underlying Coval conversations and runs—and present the whole document as a slide deck.

### Start from a suggested idea

When you open a blank notebook, the Sofia sidebar suggests a few ideas to start from. Select one to place its full prompt in the message box, edit it to fit what you need, then press **Send**. Nothing is sent until you do. Select **More ideas** to see others.

Expand an idea below to see its prompt and a deck Sofia built from it in one of Coval's demo organizations. Your results depend on the data in your workspace: when recent activity is thin, Sofia says which period it used instead.

> [accordion] This week, in six slides
>
> A weekly team briefing you can present: what you tested, what improved, what regressed, the conversations everyone should see, open questions, and next steps.
>
> ```text Prompt wrap theme={null}
> Make a six-slide weekly briefing I can present to my team: what we tested, what improved, what regressed, the conversations everyone should see, open questions, and what we do next. Use this workspace's results from the last seven days (go back further if it's been quiet, and say so). Give each slide a short headline, a few bullets, and a chart or a real quote with a link. Add a cover illustration that fits our agent. Write it for someone who hasn't been following along.
>
> Repeat this every week at 8:00 AM America/Los_Angeles.
> ```
>
> Example output from the Coval Banking demo organization, shown in **Present** mode:
>
> ![Weekly briefing cover slide with a bank-vault illustration and four summary bullets](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-briefing-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=c63558b416582756f26730c431197ff9)
>
> The cover: a generated illustration for the agent and a summary of a quiet week, with Sofia saying how far back it looked.
>
> ![Slide headed Expected-behavior score rose to 75% with a bar chart comparing two runs](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-briefing-chart.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=7aeaa06aae13ebde8e8f413d973ff93d)
>
> Each slide's headline states its takeaway, with a chart comparing matched runs and links to both.
>
> ![Slide headed Two conversations everyone should see with a quoted agent line and a source link](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-briefing-quote.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=1c31766e10084e0af333f0209ae0e553)
>
> The conversations worth reviewing, with a real quote and a link to the source conversation.

> [accordion] Daily wins and fails
>
> A standup deck with a scorecard and the day's best and worst moments, each with a real quote, a link, and a line on why it worked or didn't.
>
> ```text Prompt wrap theme={null}
> Make a daily wins and fails briefing as slides I can present at standup. Look at yesterday's simulations and conversations in this workspace (if yesterday was quiet, use the most recent day with activity and say which). Slides: a cover with an illustration that fits our agent; a scorecard charting the key metrics, against the day before if that day had activity; the three best moments; the three worst moments; and what to do next. Give each moment a short real quote, a link to the conversation and one line on why it worked or didn't, and pick different kinds of moments rather than repeats of one problem. Give every slide a headline that states its takeaway and a few bullets. Keep chart labels short.
>
> Repeat this every day at 8:00 AM America/Los_Angeles.
> ```
>
> Example output from the Coval Hospitality demo organization, shown in **Present** mode:
>
> ![Daily wins and fails cover slide with a hotel front-desk illustration](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-wins-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=5ac9dece58353da6aa3556c3b0619a44)
>
> Yesterday was quiet, so Sofia used the most recent active day and said so on the cover.
>
> ![Slide headed Volume tripled, but clean-run reliability fell sharply with two bar charts](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-wins-scorecard.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=7d28c0136eee8f28037f9dabe1be1d2a)
>
> The scorecard charts volume and reliability against the day before.
>
> ![Slide listing three best moments with quoted agent lines and source links](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-wins-best.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=1bf5374d92863f347ec0e8db6685daa0)
>
> The best moments, each with a quote, a source link, and why it worked.

> [accordion] What should we test next?
>
> Proposed test cases for the agent with the most simulation results, each backed by a real conversation, with the gaps in today's coverage.
>
> ```text Prompt wrap theme={null}
> Make a slide deck recommending the tests we should add next. Pick the agent with the most simulation results in this workspace and tell me which one you chose. Read its current test sets and its recent failed or low-scoring simulations, then propose up to six new test cases that cover real gaps. Open with a cover illustration that fits our agent and a slide charting how it scores today by scenario, naming the areas no test covers. Give each proposed test its own slide: the scenario, what the caller says, the behavior that should pass, and a real quote, with a link, from the conversation that shows why it's worth adding. Finish with the first three to run. Give every slide a headline that states its takeaway and a few bullets. Keep chart labels short, and don't add a chart just to fill a slide.
> ```
>
> Example output from the Coval Banking demo organization, shown in **Present** mode:
>
> ![Cover slide headed Cassidy needs stronger guardrail regressions, not more happy paths](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-test-next-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=a279a364977270d713fd7ade88ab8370)
>
> Sofia names the agent it chose and why.
>
> ![Slide charting conversation success by scenario with a list of untested behaviors](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-test-next-coverage.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=a8c5fe924e17272b5e454c370c3378cd)
>
> How the agent scores today by scenario, and what no test covers yet.
>
> ![Slide describing a proposed wire-correction test with a quoted agent line and a source link](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-test-next-slide.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=b2fb89bbd37bfa345b773b91e16a5c75)
>
> One proposed test per slide: the scenario, what the caller says, the behavior that should pass, and the conversation that motivated it.

> [accordion] New issues worth fixing
>
> The investigation findings that matter most, ranked, one per slide with evidence, a likely cause, and a next step.
>
> ```text Prompt wrap theme={null}
> Make a slide deck of the new issues worth fixing. Look at the investigation findings first seen in this workspace in the last seven days (go back further if it's been quiet, and say so) and pick the five that matter most, by customer impact and how often they recur. Open with a cover illustration that fits our agent and a slide that ranks the five in a chart. Give each issue its own slide: a one-line summary, a real quote with a link, the likely cause (labelled as a hypothesis) and the best next step. End with what to fix first. Give every slide a headline that states its takeaway and a few bullets. Keep chart labels short, and don't add a chart just to fill a slide.
>
> Repeat this every week at 8:00 AM America/Los_Angeles.
> ```
>
> Example output from the Coval Insurance demo organization, shown in **Present** mode:
>
> ![Cover slide headed Five issues are driving the most customer risk](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-issues-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=445d8b0351489a4387844fb1223ef6a8)
>
> No new findings in the last week, so Sofia widened the window to 30 days and said so.
>
> ![Slide headed Claims are filed before required facts are collected with a quoted agent line](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-issues-detail.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=7e3491d2a1ae602542441f1c78e1ae53)
>
> Each issue gets a quote from a real conversation, a hypothesis, and the best next step.

> [accordion] Did our change help?
>
> A before-and-after comparison of two comparable runs: what changed between them, whether scores moved, and whether to keep the change.
>
> ```text Prompt wrap theme={null}
> Make a before-and-after slide deck for the two most recent comparable runs of one agent in this workspace, preferring a pair that shares several test cases. Slides: a cover with an illustration that fits our agent; which agent and runs you picked, what changed between them (agent version, prompt, model or settings, or that nothing recorded changed) and whether the comparison is fair (same test set, personas and metrics); the metric changes; the cases that got fixed; the cases that broke; a real quote with a link from each run; and a clear call to keep the change, dig deeper, or gather more evidence. Give every slide a headline that states its takeaway and a few bullets, chart the numbers wherever a slide has them, and keep chart labels short. If there is no fair pair, show me what's missing instead.
> ```
>
> Example output from the Coval Banking demo organization, shown in **Present** mode:
>
> ![Cover slide headed The later run looks better but the evidence is too thin to keep the change](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-change-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=c3d6f6828de8d3a81bbcf9c6e29ad194)
>
> The recommendation up front: the later run looks better, but the evidence is too thin to keep the change.
>
> ![Slide headed No agent change is recorded with a chart of metrics per conversation](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-change-what-changed.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=78506e024e375c21d4f7bc92585a5b1c)
>
> What changed between the runs. Here no agent change was recorded, and Sofia says so.
>
> ![Slide headed No case was fully fixed with a chart of scores by case and run](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-change-by-case.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=14e08fa72a9a3627db9f2c5cc133a4dd)
>
> Case-by-case results show which cases were fixed, improved, or held.

> [accordion] Where customers get stuck
>
> Recurring friction patterns in recent conversations, how often each appears, a real example, and the first fix to make.
>
> ```text Prompt wrap theme={null}
> Make a slide deck showing where customers get stuck with our agent. Read the most recent conversations in this workspace from the last seven days (go back further if it's been quiet, and say so) and group the moments where things went sideways: repeated questions, misunderstandings, dead ends and unnecessary handoffs. Open with a cover illustration that fits our agent and a slide charting the patterns by how often you saw them. Give each of the top three to five patterns its own slide: a real quote, a link to the conversation, how often it came up in what you read, and one concrete fix. End with the fix to make first. Give every slide a headline that states its takeaway and a few bullets. Keep chart labels short, and don't add a chart just to fill a slide.
>
> Repeat this every week at 8:00 AM America/Los_Angeles.
> ```
>
> Example output from the Coval Restaurant demo organization, shown in **Present** mode:
>
> ![Cover slide headed Callers lose confidence when Tony forgets, fragments, or defers](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-stuck-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=e5b4573acb8a432a0a5171c80b279fdf)
>
> The cover names the pattern and notes where the conversations came from.
>
> ![Slide headed Wrong details are the biggest trust breaker: 8 of 20 conversations](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-stuck-pattern.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=61e2720f5da957855f75907075998c18)
>
> One pattern per slide, with how often it appeared, a transcript excerpt, and a concrete fix.

> [accordion] Weak spots behind averages
>
> Segments that score worse than the overall average, with sample sizes, small-sample warnings, and the test that would confirm each gap.
>
> ```text Prompt wrap theme={null}
> Make a slide deck of the weak spots our averages are hiding. Using the last seven days of results in this workspace (go back further if it's been quiet, and say so), break the key metrics down by whatever dimensions exist here, such as test case, persona, scenario type or agent version. Open with a cover illustration that fits our agent and a slide charting the overall numbers. Give each of the three biggest gaps its own slide: a chart of the segment against the average, the sample size, and a real quote with a link showing what's going wrong. Flag any segment too small to trust. End with the next test that would confirm each gap. Give every slide a headline that states its takeaway and a few bullets. Keep chart labels short.
>
> Repeat this every week at 8:00 AM America/Los_Angeles.
> ```
>
> Example output from the Coval Retail demo organization, shown in **Present** mode:
>
> ![Cover slide headed Averages hide three return-flow gaps](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-weak-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=d0aafdf8a5015f15346bc546977156a9)
>
> The cover sums up what the averages hide.
>
> ![Slide headed Only 1 in 9 calls completed the workflow with a bar chart of overall results](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-weak-overall.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=106ac70e74f616c5802b3574e93957b4)
>
> The overall picture first, with scope and how far back Sofia looked.
>
> ![Slide headed Gap 1, the full return path scored 0% success, with a chart and a quoted agent line](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-weak-gap.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=92841abc9642ac198518e8df2d3acdf9)
>
> One gap per slide: the segment against the average, its sample size, the next test, and a quote.

> [accordion] Why is our agent slow?
>
> The slowest recent conversations compared with normal ones, where the time went, and the fixes most likely to help.
>
> ```text Prompt wrap theme={null}
> Make a slide deck on why our agent is slow. Find the slowest recent conversations in this workspace and compare them with a few normal ones. Slides: a cover with an illustration that fits our agent; a chart of response latency, slow against normal; a chart of one slow conversation turn by turn, showing where the time went; the biggest delays you found, each with a quote and a link; the fixes most likely to help, ranked; and what timing data is missing. Split agent thinking time, tool calls and speech where the data supports it. Give every slide a headline that states its takeaway and a few bullets. Keep chart labels short, and don't add a chart just to fill a slide.
> ```
>
> Example output from the Coval Hospitality demo organization, shown in **Present** mode:
>
> ![Cover slide headed Remy's slowest sampled call spent too long thinking, and then said too much](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-slow-cover.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=2c15507d8a2e3626ab0cc8d1fbfd0271)
>
> The cover names what made the slowest call slow and the sample Sofia looked at.
>
> ![Slide headed The slow case waited 6.1s to answer with a bar chart of answer gaps](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-slow-vs-normal.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=3a512e6a20bcbe0f72bb0d109a0c4b64)
>
> Response latency for slow and normal conversations, with links to each.
>
> ![Slide headed One 30.2s answer turn dominated the 46.0s slow conversation with a bar chart of time per turn](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/starter-slow-turns.jpg?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=6c1db5d856f6291953314047e1cd485b)
>
> One slow conversation turn by turn, with the trace evidence behind it.

Recurring ideas end with a line such as "Repeat this every week at 8:00 AM" in your timezone. Keep it to have Sofia schedule future editions (see [Schedule recurring notebooks](#schedule-recurring-notebooks)), or delete it for a one-off notebook.

## Create and edit a notebook

You can start a blank notebook from the **Notebooks** page or ask Sofia in chat to turn an investigation into a notebook or presentation. Every notebook opens as a rich-text canvas with Sofia docked in the sidebar so you can write by hand and ask Sofia to add, revise, or reorganize sections in the same place.

* **Rich-text structure and blocks**: Format headings and text, and use tables, checklists, multi-column sections, collapsible sections, charts, and grounded citations that link directly to simulations, conversations, runs, and metrics in your workspace. Insert slide breaks, columns, and collapsible sections from the toolbar, or ask Sofia to add tables, charts, and citations.
* **Continuous autosave**: Changes save automatically as you type. While Sofia is actively updating the notebook, a banner lets you know direct editing is temporarily paused, and any follow-up prompts you send queue in the sidebar until the update finishes.
* **Lock and unlock**: Lock the notebook from the toolbar when you want to read or review without accidental edits, and unlock it when you are ready to keep writing. A locked notebook also blocks Sofia's edits and version restores.
* **Revision history and conflict recovery**: Open **Activity** to preview and restore saved versions (up to the 50 most recent revisions). If another tab or session saved a newer version first, Coval keeps your draft in the editor and shows the saved version so you can compare them, then choose **Keep editing my draft**, **Use saved version**, or **Save my draft instead**.

## Schedule recurring notebooks

When you want an analysis, scorecard, or executive review to stay current automatically, put a saved notebook on a recurring schedule. Select **Repeat** in the notebook header, or ask Sofia in the notebook sidebar to schedule it.

1. Choose how often it repeats: every *N* days, weeks, or months.
2. Set the time and timezone for each run.
3. Optionally add instructions for future editions—such as which metrics or agents to prioritize—then select **Schedule notebook**.

Saving the schedule captures the notebook's current content as the template for future editions. If you edit the original notebook later, open **Repeat** on it and select **Save schedule** so future editions use your changes.

On each scheduled run, Sofia conducts fresh research over your workspace's latest simulations, conversations, and runs while preserving your original notebook's structure, tone, and formatting. Your original notebook remains unchanged, and each scheduled run publishes a new dated edition.

New editions inherit the series' visibility, which starts as the original notebook's visibility (**Only me** unless you shared it). Changing **Share** on the original notebook updates the series, so its existing and future editions use the new setting. Changing **Share** on a single edition affects only that edition.

In the **Notebooks** list, recurring notebooks are grouped into a single series row showing the cadence (or **Paused**), the number of editions, and when the latest edition was saved. Select a series to see its next scheduled run, browse its editions, and open any edition or the original notebook. To change or pause the schedule, open the original notebook or any edition and select **Repeat**. To resume a paused schedule, select **Schedule notebook** in the same dialog.

> [!TIP]
>
> To notify your team in Slack whenever a scheduled notebook edition finishes, ask an organization admin to enable **Scheduled notebook notifications** on a Slack channel binding. See [Scheduled notebook notifications](https://docs.coval.ai/sofia/slack-beta.md#scheduled-notebook-notifications).

## Add images, GIFs, and video

Select **Add media** in the notebook toolbar to embed visual examples, recordings, or diagrams alongside your findings:

* **Supported sources**: Paste a public `https://` link to an image, an animated GIF, or a direct `.mp4` or `.webm` video file. YouTube and Vimeo pages are not supported. Animated GIFs keep their animation in the notebook and in **Present** mode. Each media block needs a short description, which is used as its alt text.
* **Playback and layout controls**: Resize media blocks to fit your layout. For videos, you can enable looping, attach an optional `https://` poster image, and attach optional `https://` English captions (`.vtt`). Video playback always starts when the viewer clicks play.
* **Caption CORS requirement**: When a video includes captions, the browser loads both the video and the caption track with anonymous cross-origin checks, so both hosts must return `Access-Control-Allow-Origin` headers.

![Animated GIF spinning inside a Sofia notebook slide in Present mode](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/notebook-in-motion.gif?s=e4d53991b53ae1c8046b93770fb7918e)

An animated GIF embedded in a notebook slide in Present mode, preserving its full animation.

![Video block playing inside a Sofia notebook slide in Present mode](https://mintcdn.com/coval-2e18a559/vIMEQ1e7lI7Adn-o/images/sofia-notebooks/notebook-video-player.png?fit=max\&auto=format\&n=vIMEQ1e7lI7Adn-o\&q=85\&s=adcbfeb115d08168b10bacedc2972ab0)

A native video block playing inside Present mode with playback, volume, and fullscreen controls.

> [!NOTE]
>
> Media loads directly in each viewer's browser from the URL you provide. Anyone who can view the notebook—including through a shared link or revision history—can see the full media URL, including any signed query parameters. Use durable links intended for your notebook's audience, and avoid URLs that embed private credentials.

## Present as slides and export to PDF

Any notebook can be presented as a slide deck without copying your work into another tool.

**1. Open Present mode**

Select **Present** in the notebook toolbar. The notebook fills the window and divides your content into slides at its slide breaks; a notebook without slide breaks starts a new slide at each level 1 or level 2 heading. Collapsible sections are shown expanded, and charts, media, and source links stay in order. Any video playing in the document pauses automatically when you enter **Present**, and leaving a slide stops its video player.

**2. Navigate the deck**

Move between slides with the previous/next controls, the slide picker, or your keyboard's arrow keys. Video player keyboard shortcuts stay scoped to the player so they do not accidentally advance slides. Press **Escape** to return to the notebook canvas.

**3. Export to PDF**

While in **Present** mode, select **Export PDF** to download the deck as a 16:9 landscape PDF with one page per slide. Charts, multi-column layouts, and illustrations are captured as they appear on screen, oversized slides scale to fit, and links to simulations, conversations, and external sources remain clickable. Slide text is captured as an image; use **Accessible PDF** when you need selectable text.

PDFs cannot play media. In both **Export PDF** and **Accessible PDF**, each video appears as its poster image (when set) with a labeled link to the original video. **Export PDF** also replaces any image whose host does not allow cross-origin capture with a labeled link to the original image and warns you after the download; animated GIFs export as still frames. To print or save the notebook document itself, select **Accessible PDF** on the canvas, which opens your browser's print dialog.

## Share a notebook

Select **Share** in the notebook header and choose who can read the notebook through its link:

| Option | Who can read the notebook |
| - | - |
| **Only me** | Only you. This is the default, and choosing it revokes any existing link. |
| **This workspace** | Signed-in members with access to the notebook's workspace. |
| **This organization** | Signed-in members with access to your organization. |
| **Anyone with the link** | Anyone who has the link, without signing in. Review the content before you select **Make public**. |

After you save the new access, select **Copy link** and send the link to your readers. Sharing does not add the notebook to their notebook lists.

* Shared views are read-only. Only the owner can edit, rename, delete, or change sharing. Changing access replaces the link, and deleting the notebook revokes it.
* Shared views include the saved document, tables, charts, and media, but not your original prompts or Sofia's research steps. They preserve **Present** mode, media playback, and links back to the underlying Coval runs, simulations, and conversations. Linked simulations and traces keep their own permissions.
* When you open your own shared link while signed in, the header shows **Edit with Sofia** (or **Open notebook** when the notebook cannot be edited there) to return to the editable notebook. Other readers see only the read-only view.
* For recurring notebooks, see [Schedule recurring notebooks](#schedule-recurring-notebooks) for how sharing applies to editions.


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