> For the complete documentation index, see [llms.txt](https://docs.hamina.com/hamina/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hamina.com/hamina/guides.md).

# Guides

- [Working in Teams](https://docs.hamina.com/hamina/guides/working-in-teams.md): Learn how to effectively work with teams of people in Hamina Network Planner and Hamina Onsite.
- [Scaling Maps](https://docs.hamina.com/hamina/guides/scaling-maps.md): Learn how to scale maps in Hamina Network Planner.
- [Managing Maps and Floors](https://docs.hamina.com/hamina/guides/maps-floors.md): Learn how to switch, rename, and manipulate maps in Hamina Network Planner.
- [Replacing Maps](https://docs.hamina.com/hamina/guides/replacing-maps.md): Learn how to replace maps for existing projects in Hamina Network Planner.
- [Surveys to Design](https://docs.hamina.com/hamina/guides/surveys-to-design.md): Learn how to use site survey measurements to create network designs in Hamina Network Planner.
- [Channel Planning](https://docs.hamina.com/hamina/guides/channel-planning.md)
- [Private Cellular Planning](https://docs.hamina.com/hamina/guides/cellular-planning.md): Learn about Hamina's private cellular planning capabilities.
- [Outdoor Planning](https://docs.hamina.com/hamina/guides/outdoor-planning.md): Learn how to perform outdoor planning in Hamina Network Planner.
- [Mesh Planning](https://docs.hamina.com/hamina/guides/mesh-planning.md): Learn how to plan for mesh links with Hamina Network Planner.


---

# 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://docs.hamina.com/hamina/guides.md?ask=<question>&goal=<user_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.