> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/getting-started/navigating-the-ui/sharing-analytics.md).

# Microsites: Share your AlphaGeo dashboard

Share dashboards with external collaborators.

Microsites allow you to share your AlphaGeo dashboard directly with collaborators, including with stakeholders who do not have an AlphaGeo subscription or account. They provide a more interactive experience than PDF or Excel exports. Collaborators can view your data filters, charts, visualizations, and platform features such as the Remediation Checklist.

Click through the following sub-pages to learn how to create, share, access, and navigate microsites:

* [Creating and sharing microsites](/getting-started/navigating-the-ui/sharing-analytics/creating-and-sharing-microsites.md)
* [Accessing and viewing microsites](/getting-started/navigating-the-ui/sharing-analytics/accessing-and-viewing-microsites.md) (hint: share this page with external collaborators who are new to AlphaGeo and need support with their microsite)

{% hint style="warning" %}
Changes to the underlying data appear in any active shared link until it expires.

Set filters before you share. Always set an expiration date to reduce the risk of exposing confidential data.
{% endhint %}


---

# 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.alphageo.ai/getting-started/navigating-the-ui/sharing-analytics.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.