> 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/accessing-and-viewing-microsites.md). # Accessing and Viewing Microsites Use the **guided demo** below to learn how to access and navigate an AlphaGeo microsite that has been shared with you. ### Guidelines Because microsites are often shared with recipients who are not AlphaGeo customers, certain restrictions apply: * Microsite recipients can only see the filtered view you share with them. They cannot see any assets or portfolios that have been filtered out. * Microsite recipients can access the following features: * **Portfolio Analytics**: Multi-asset view and Single-asset view * **Asset Remediation Checklist**: Use microsites to share asset checklists with recipients. Any answers saved by a recipient also appear in your dashboard and are saved to the relevant asset and portfolio. * The following features are not available to microsite recipients: * **Location Explorer**: The ability to search for and add new assets is limited to AlphaGeo subscribers only. {% embed url="" %} --- # 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/accessing-and-viewing-microsites.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.