> ## Documentation Index
> Fetch the complete documentation index at: https://docs.libratech.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Collaboration
> Share drafting templates, themes and drafts, and work through redlines and comments with colleagues, the counterparty and Libra.
Drafts rarely stay with one person. You share templates with the team, send a draft to a partner for review and negotiate over the counterparty's redlines, all in the Editor.
## Share a template and its theme
Share a drafting template from its **⋯** menu in **Templates** › **Drafting**, or with **Share** in the template editor. You share with people and groups, or with the whole team under **General access**, as with any template.
| Access | What the recipient can do |
| - | - |
| View | Open the template read-only, and **Use** it to start drafts |
| Edit | Also change the template and its theme, and share it further |
Only the author can delete a template. A recipient who no longer needs it can **Remove from my templates**, and stars stay personal to each user.
A theme is only ever shared through the templates that use it. The recipient sees it tagged **Shared** and can apply or duplicate it; with edit access, they can change it for everyone. For the sharing dialog itself, see [Starring & sharing templates](/en/features/templates/starring-and-sharing).
## Share a draft
**Share** in the document menu (click the draft's name in the title bar) shares the draft's project, not just the draft. Everyone you add gets the whole project, including this draft, while your chats stay private.
Choose **Can view**, **Can edit** or **Full access**, or open the project to **Everyone in the team**. [Sharing & access](/en/features/sharing-and-access) explains the levels.
**Share** becomes available after the first save, and teams of one don't see it. What each person sees depends on what you've published: see [Publish](/en/features/drafting/editor#publish).
## One editor at a time
Two people can't edit the same draft at the same moment. If a colleague saves while you have it open, a banner tells you, such as *Anna saved a new version of this document*, and the last save wins.
Agree who edits when. [Version history](/en/features/drafting/editor#version-history) keeps every saved state if you need to go back.
## Editing or Suggesting
The switch at the right end of the toolbar sets how changes land, yours and Libra's alike.
| Mode | Your typing | Libra's changes |
| - | - | - |
| **Editing** | Goes straight into the document | Go straight in; review them with **Show changes** |
| **Suggesting** | Becomes a redline, with insertions underlined and deletions struck through | Arrive as redlines, sometimes with a comment saying why |
Suggesting tracks your typing, new and merged paragraphs, images and line breaks. Alignment, spacing, indents, lists and paragraph styles become suggestions too. Tables, footnotes and page or column breaks need **Editing**, and bold, fonts, colours and **Theme** go in untracked, as in Word.
## Work through redlines
Open the counterparty's Word file from Project files, and their tracked changes and comments appear in the margin, just as in Word.
Each suggestion has a red marker in the margin, and comments a blue one. Click a marker or the marked text, and its card opens in the **Comments & Suggestions** tab on the right.
You accept or reject on the bar at the bottom of the page.
1. **Accept**, or **Reject**, on the bar
2. **Ask about this change…**, a thread for your colleagues
3. **Accept all**
* The bar steps through every suggestion with **‹** and **›**, in **Editing** and **Suggesting** mode alike. **✕** hides it.
* With a suggestion or comment selected, **↑** and **↓** move between them, **Enter** accepts or resolves, and **Backspace** rejects or deletes your own comment.
* **Ask about this change…** on a suggestion card starts a thread with your colleagues. It doesn't ask Libra.
To have Libra do the first pass, select the section and ask in the Editor chat: *"Go through the counterparty's redlines in clause 9, accept the typo fixes and tell me which ones shift liability to us."*
Libra reads every redline and comment, and accepts or rejects one only after you've decided. When it rewrites a passage that carries someone else's redline, **Editing** mode accepts their change first, and **Suggesting** mode proposes the rewrite as a suggestion of its own.
## Comments
Select text and click **Add comment** in the margin, or **Comment** on an image. Colleagues reply in the thread, **Resolve** closes it and **Reopen** brings it back. You can edit or delete your own comments.
1. The comment’s marker in the margin
2. The thread in the right panel, with **Resolve** at the top right and the **Reply…** box below
3. The marker of a suggestion on the same clause
Commenting needs edit access to the project, and a comment saves the moment you post it. There are no @mentions or notifications yet, so tell a colleague when a comment is for them.
## The Comments & Suggestions tab
The **Comments & Suggestions** tab in the right panel lists every comment and suggestion in the draft. Filter by **All**, **Comments**, **Suggestions** or **Resolved** (← and → switch filters), and click a row to expand it in place.
**All** lists them in the order they appear in the document.
A comment whose text has since been deleted stays in the list, marked *Anchor text no longer in the document*.
## Next steps
What the Editor chat can change, and how to check its work.
How project sharing and its access levels work.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.