> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/team-collaboration/documents.md). # Collaborative Documents ## Every document, shared with your team and their agents Markdown, mockups, diagrams, and more, edited together in real time or asynchronously. Each teammate's locally running Nimbalyst and configured agents work in the same shared files, not separate copies. See [collaborative documents in Nimbalyst Teams](https://nimbalyst.com/teams/documents/) for how shared editing works.

Two teammates editing the same markdown document in real time, with presence and a live labeled cursor — True multiplayer editing keeps everyone on one shared copy.

### Everyone in the same document at once

Two teammates editing the same document with presence avatars and a live labeled cursor — Presence avatars and labeled cursors show who is in the document and where they are working.

* **True multiplayer:** Type in the same markdown, mockup, or diagram at the same time, with a live cursor for every person in the document. * **See who is here:** Presence avatars show who is in the document and where they are working right now. * **Your agents, in the same file:** Each teammate's local Claude Code and Codex agents edit the same shared document, so people and agents stay on one copy. ### One document, every kind of content inside it Shared documents are not limited to text. Embed a mockup, diagram, image, or inline tracker in the page and edit it in place.

A shared document with a UI mockup embedded inline and a live cursor — The embedded mockup remains editable inside the shared document.

* **Markdown, mockups, and diagrams:** Work in shared markdown, UI mockups, Excalidraw, Mermaid, mind maps, data models, and spreadsheets in one workspace. * **Embed anything inline:** Drop an Excalidraw canvas, mockup, image, or other supported extension file into a document and edit it inline. * **Inline trackers:** Add an editable tracker reference inside a document so the plan and the task remain connected. Type `@` to choose a project file. Put the file reference by itself in a paragraph and Nimbalyst upgrades compatible editor types into a live inline embed.

A shared markdown document containing two live embeds, a mockup showing a tracker board and an Excalidraw diagram, each with a header naming its shared path and an Open action — Embedded files render live inside the shared document. Each embed names its shared path and opens in its own editor.

An embed inside a shared document is a live view of another shared file, not a flattened image. The mockup and the diagram above are still their own documents. Anyone with access can edit them in place, or click **Open** to work on them in the full editor, and the change appears everywhere the file is embedded. ### Sharing a document that contains embeds When you share a markdown file that embeds other files, those embedded files have to be shared too. Otherwise your teammates would open the document and find empty placeholders where the mockup and diagram should be. Nimbalyst handles this in the **Share to Team** dialog. It scans the document for embedded files and lists each one under **Linked documents**, pre-checked.

The Share to Team dialog showing the source file, shared name, destination folder tree, and a Linked documents section listing an embedded mockup and an Excalidraw diagram, both checked and marked Already shared — Share to Team finds the files a document embeds and shares them alongside it.

* **Everything the document needs, in one action:** Leave the linked documents checked and Nimbalyst shares them with the parent document, so the embeds render for everyone. * **Already-shared files are recognized:** An embedded file that is already in the team space is marked **Already shared** and is reused rather than duplicated. * **You stay in control:** Uncheck any linked document you do not want in the team space. Its embed will show as unavailable for teammates until you share it. * **The count reflects your choices:** The confirm button tells you how many documents are about to be shared. Embedding works the same way in a tracker item body. See [Collaborative Trackers](/team-collaboration/trackers.md). ### Supported Shared File Types Nimbalyst can share and co-edit: * Markdown, plain-text, and code files such as TypeScript, HTML, Swift, and Python * Excalidraw diagrams and supported visual diagrams * Mockups * CSV, TSV, and calc spreadsheets * Data models * Other extension file types that declare collaboration support The editor determines how collaboration appears. Text and code show live cursors and selections, spreadsheets show the selected cell and active editor, and visual editors can show canvas selections and presence. ### Promote any local file to shared in a click

The file context menu open on a document, with a Share to Team action — Start locally, then choose Share to Team when the file is ready for collaboration.

1. In Files mode, right-click the local file. 2. Choose **Share to Team**. 3. Choose its shared name and destination folder. 4. Confirm **Share to Team**. Only what you choose is shared. Your code and other local files remain on your machine. Nimbalyst keeps a link to the originating local file so you can open, relink, or re-upload it when needed. The shared copy flows through Nimbalyst's Cloudflare sync service and is encrypted in transit and at rest. Teammates who return later receive the changes made while they were away and can continue with their own local agents. ### Work Offline Previously opened shared documents open immediately from an encrypted local copy when the network is unavailable. You can continue editing text, supported visual content, and attachments while offline. Nimbalyst keeps document changes and attachment uploads in a durable queue. When the device reconnects, it uploads the queued work and merges it with changes received from teammates. The queue survives a window or application restart. Documents you have never opened still require a connection for their first download. An attachment that is not yet cached shows an unavailable placeholder until Nimbalyst can retrieve it. ### Discuss the work right where it lives

A shared document with a highlighted passage and a comment thread with a reply — Comments keep review feedback beside the exact passage being discussed.

* **Comment in context:** Leave a comment on a passage or section so feedback sits next to the thing it is about. * **Threads that resolve:** Reply, resolve, and reopen threads so review happens in the document instead of a separate chat. * **Everyone stays in sync:** Comments sync in real time so the whole team sees the discussion as it happens. ### Never lose a version

Document History for a shared document, showing a saved revision, its author and metadata, and a Restore as Current Version action — Review saved revisions and restore the one you need without leaving the shared document.

* **Full change history:** Every shared document keeps its history so you can see how it changed and who changed it. * **Restore in one click:** Roll a document back to an earlier version without leaving the editor. * **Review before you trust:** Scan what changed since you last looked so nothing slips by unnoticed. Right-click a document in the Collaboration sidebar and choose **View History**. Press **Cmd/Ctrl+S** in a shared document to save a revision. ### Find shared work in the Shared home **Shared home** lists every document in the team space in one sortable table, with the folder tree beside it.

The Shared home view listing shared documents in a table with Name, Type, Created by, Last edited, Viewed by me, and Folder columns, filter tabs for All, Favorites, Unread, Recently opened, Shared with me, and Shared by me, and unread dots beside several rows — Shared home lists every shared document with its type, folder, author, and when you last looked at it.

* **Sort by any column:** Name, type, who created it, when it was last edited, when you last viewed it, and which folder it lives in. * **Filter to what matters:** **All**, **Favorites**, **Unread**, **Recently opened**, **Shared with me**, and **Shared by me**, with a count on the unread filter. * **Narrow further:** Filter by type, by person, or by folder, and search across every shared document. * **List or tiles:** Switch between the table above and a tile view from the toggle at the top right. ### Favorites, and what changed since you were last here

A shared folder in the Collaboration sidebar, with gold stars marking three favorited files and blue dots marking two files that changed since they were last opened — A gold star marks a favorite. A blue dot marks a document that changed since you last opened it.

* **Favorites:** Star the documents you keep coming back to and reach them from the **Favorites** filter. Starred files show a gold star wherever they appear. * **Changed since you were away:** A blue dot marks each shared document that changed since you last opened it. Opening the document clears the dot. * **New and recently updated:** Use the **Unread** and **Recently opened** filters to catch up on what moved while you were away, sorted by the last change. The Collaboration sidebar also provides shared folders, search, drag-and-drop organization, and **All**, **Favorites**, and **Updated** filters. ### Open shared documents in a browser Shared markdown documents also open at [console.nimbalyst.com](https://console.nimbalyst.com), where teammates can edit them live and comment without installing the desktop app. See [Web Console](/team-collaboration/web-console.md). --- # 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.nimbalyst.com/team-collaboration/documents.md?ask=&goal= ``` `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.