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

# GitBook

> Search and read your GitBook runbooks, and have Neo draft documentation updates in change requests for review

GitBook holds your documentation: spaces of pages such as runbooks, process docs and client guides, changed through change requests that a person reviews and merges. Connect your GitBook organization once with a personal access token, and Neo agents can find and read your runbooks, and draft new or updated pages for your team to review.

## What Neo can do with GitBook

* Search every space for a runbook, by customer and task, and read the page as markdown
* Answer a technician's question in chat with the steps from your runbook, and a link to it
* Draft a new or updated page from a ticket's outcome, a meeting note or a technician's draft, in a change request, and ask a person to review it
* Merge a change request when your instructions or the technician say so, with a technician's approval if you keep it on
* Read what visitors asked your docs site's Ask AI, the documentation issues GitBook found, and the audit trail

## Publishing waits for a technician in Helpdesk and IT Admin

Neo edits pages through change requests, and a change request is a draft until someone merges it. Merging sits in its own permission group, **Publishing & Export**: the Helpdesk and IT Admin profiles ask a technician before each merge, and Full Automation does not. A few writes in **Spaces, Pages & Search** change live content directly: applying a template, importing a website or running a translation into a space, and deleting a space. So for an agent that must only draft, keep Spaces, Pages & Search at Read Only, as Helpdesk does, and leave Publishing & Export off. Granting or changing access, changing who can see or edit a site or space without review, creating or changing a share link or visitor authentication, and installing an integration always ask a technician, in every profile; removing access and deleting a share link or a connection follow the group's approval setting.

## Who your customers are

GitBook's API has no list of your customers: your spaces hold your own documentation. The agent finds a customer's runbook by searching for the customer's name, so there is no Organization Mapping tab.

## Next steps

> [card] [Connect GitBook](https://docs.neoagent.io/integrations/gitbook/connecting-to-neo.md)
>
> Create a personal access token and save it in Neo.

> [card] [GitBook API](https://docs.neoagent.io/agents/tools/documentation/gitbook-api.md)
>
> The permission groups and access profiles.


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