> ## Documentation Index
> Fetch the complete documentation index at: https://reconco.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://reconco.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://reconco.manicule.dev/api/mcp.
> Every agent surface: https://reconco.manicule.dev/.well-known/llms-manifest.json

# Key Concepts (/documentation/get-started/key-concepts)

<!-- agent-signals: reading_time_min: 2 · est_tokens: 514 · updated: 2026-11-22 -->
Related: [Introduction to Reconco](/documentation/get-started/introduction-to-reconco.md), [How Reconco Works](/documentation/get-started/how-reconco-works.md)

Reconco is a documentation tool for teams, used through a web app. When evaluating it, distinguish how documentation is organized from who can access it. These are general documentation concepts, not a glossary of confirmed Reconco features or object names.

## Understand content and organization

Documentation content is the information a team needs to communicate. For example, an explanation of a service's behavior and instructions for changing its configuration serve different reader needs, even when both concern the same service.

Content organization determines how readers find that information and understand its relationship to other material. Grouping by service can help someone find everything about a system they maintain. Grouping by task can help someone complete a change that involves several systems. These are ways to assess whether an arrangement fits your team's work, rather than claims about how Reconco structures content.

Use a familiar documentation task to evaluate organization: could a developer find the instructions they need and distinguish them from background explanation? Terms such as workspace, project, or page do not by themselves establish an answer. Do not assume Reconco uses those names or nests content in that order.

## Separate organization from access

Grouping related content answers where it belongs. Access answers who can read or change it. A useful grouping does not, by itself, establish a permission boundary.

For example, a team might want related service documentation grouped together while restricting changes to a smaller set of contributors. That is an evaluation requirement, not a statement that Reconco supports a particular permission model.

Assess content navigation and access separately. Confirm what readers can view, what contributors can change, and whether sharing affects either. Reconco's membership rules, sharing defaults, and ownership behavior are not established here; do not infer them from a content grouping or assume that material is private or shared by default.
