> For the complete documentation index, see [llms.txt](https://guides.livingwriter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.livingwriter.com/desktop-app-+-web-version/share-manuscript-and-chapters.md). # Share Manuscript and Chapters {% embed url="" %} You can easily share your manuscript or chapters in just a couple of clicks. First, open your manuscript. Go to the top right and click on the ''Share'' option:

Or you can also click on ''Manuscript'' > Share:

You will be able to find ''Share'' as the 5th option in the dropdown. Once you have located it, click on it: As mentioned before, you can choose to share specific chapters or your entire manuscript. In this case, let's share our manuscript:

A new window will pop up in the middle of your screen, as shown in the screenshot above. You can choose to share your entire manuscript or a specific chapter:

You can share your manuscript by the link and share it with your editor or whoever you wish to share your manuscript with. And, you also have the option to share your manuscript with an invitation email. Under ''Invite With Email'', you need to type in the email or emails of the people you'd like to share your manuscript with, and you can choose the permissions you'd like them to have:

As shown in the screenshot above, you can grant different levels of access permissions, including view-only, comment, or edit rights for your manuscript. Once you have selected the desired permissions, simply click "Send Invite," and the recipients will receive an invitation via email. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guides.livingwriter.com/desktop-app-+-web-version/share-manuscript-and-chapters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.