Index BookStack books, chapters and pages so your self-hosted documentation answers questions with citations alongside chat, tickets and projects.
Representative data is enough. No production access required for the first demo.BookStack connects through an admin-defined boundary. Each object type below lists what Linkence reads, the scope condition that applies and the limitation you should know about before the first sync. Your BookStack account remains the system of record.
Page content and chapter structure
Approved shelves and booksFind · Prepare · Act
Pair BookStack with Confluence, Outline, Gitbook and the answer stops being a search result. Evidence arrives from every connected system, and the next step waits for your approval.
A cited answer that opens the exact BookStack page
Bring one of these to the demo on representative data. Every answer arrives with citations that open the original BookStack record.
Every answer reflects the verified connector behaviour, never generalised.
Admin-approved shelves and books; Scheduled sync of page content; Citations to the exact page.
Books outside the approved scope; Writing back into BookStack; Draft revisions.
Scheduled sync through the Linkence indexing pipeline. Scope: Admin-approved shelves and books.
The BookStack connector is read-focused. Writes happen through connected companions, for example a grounded reply in mail or an approved update in chat, always with approval.
We will show how Linkence finds the relevant context, presents the work and keeps every sensitive change under your team's control.
Representative data is enough for the first demo. No production access required.