> For the complete documentation index, see [llms.txt](https://help.kenyalaw.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.kenyalaw.org/working-with-a-document/document-table-of-contents-toc.md).
# Document table of contents
Efficiently navigate a document using the table of contents
You can efficiently explore a large document, by using the table of contents to navigate sections.
## To access the Table of Contents
1. Locate the legislation
2. Open the document to view the **Table of contents** on the left-hand side of the page.
3. Scroll through the **Table of Contents** using the scroll bar on the right to view the various sections.
4. Alternatively, you can use the **Search table of contents** to perform a search in the table of contents.
5. Use the "**Expand All**" and "**Collapse All**" buttons to expand or collapse all headings in your document.
6. Click on the **Chapter, Section, Part,** or **Paragraph** that contains the content you want.
7. The page will automatically jump to that part of the document.
---
# 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://help.kenyalaw.org/working-with-a-document/document-table-of-contents-toc.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.
