Skip to main content
You connect GitBook once at the MSP level, with a personal access token.

1. Create a personal access token

GitBook’s API takes a personal access token, and the token has the same access as the GitBook user who made it. So make it as a GitBook user for Neo, and give that user only the role Neo needs in your organization: an editor can draft change requests, and only a user who may merge can merge.
1

Open Developer settings

Sign in to GitBook as the user for Neo and open Developer settings (https://app.gitbook.com/account/developer).
2

Create the token

Create a personal access token and copy it. Keep it out of email and chat: anyone who has it can read and change what that user can.
Neo calls GitBook at https://api.gitbook.com/v1 with the token as a Bearer token.

2. Add it in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the GitBook card, under Documentation.
2

Save the token

Paste the token and click Save settings. Neo checks it against GitBook before saving, so a wrong or revoked token is rejected straight away.

3. Turn GitBook on per agent

Open the agent, go to the Integrations section, and pick an access profile for the GitBook block, or set each area yourself:
  • To find and read runbooks, the Read Only profile is enough.
  • To draft updates for review, use Helpdesk: the agent asks a technician before each change request it writes and before each merge. Page text can link or embed another website, and an embedded image loads when someone opens the change request, so only give a GitBook agent Full Automation when you trust everything it reads.
  • To keep an agent from ever merging or exporting, set Publishing & Export to Disabled. Keep Spaces, Pages & Search at Read Only too: applying a template, importing a website or running a translation into a space, and deleting a space, change live content directly.
These writes always ask a technician, in every profile: granting or changing access to a space, collection or site; changing a member’s role; creating a team or adding team members; inviting people or joining an organization; SSO membership; any change to a SAML provider; creating or changing a share link; changing visitor authentication or its key; adding or changing a site’s MCP server or context connection; publishing, unpublishing, installing or configuring an integration; adding or changing a Git Sync installation; transferring a collection; creating an organization or changing its settings, a site’s GitBook Agent channels or agent settings; any write that sets an access control (a visibility, a default role, a space’s edit mode or merge rules, an adaptive-content condition, SSO, email domains or invite links); any write that sets an address GitBook fetches or a visitor’s browser loads (a file added by URL, a website import, an OpenAPI source, a nav link, a logo or favicon); and deleting a site. Removing access, a team member or an invite, and deleting a share link, an MCP server or a context connection, follow the group’s approval setting. See GitBook API for what the agent can read and change.