---
title: "Indexing your own docs"
description: "How an agent indexes the team's own documentation as a private library that only that team can query."
---

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

# Indexing your own docs

Private docs are for internal libraries and runbooks. An agent indexes Markdown or text files under a library name and version:

```sh
overlane docs add our-sdk --version 3.2.0 --file docs/intro.md --file docs/api.md
overlane docs query our-sdk "retry policy" --version 3.2.0
```

## Isolation

- Private chunks (and vectors, when the optional embedding re-rank is on) live in the team's own namespace. They are never written to the shared public index and never returned to another team.
- Every record is marked `visibility: "private"` with the team's tenant ID. Public records are marked `visibility: "public"` with no tenant, so the two cannot be confused.
- When a team has private docs under the same name as a public library, that team's queries use its private docs; every other team still gets the public answer.

## Credentials

Pages are scanned before anything is stored. A page that contains what looks like a credential is refused and nothing from the call is indexed. Remove the credential and run the command again.

Indexing private docs counts as one library docs call.

Source: https://docs.overlane.app/library-docs/private-docs/index.mdx