> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/engage-link/engage-link-plazas.md). # ENGAGE LINK plazas Each ENGAGE LINK plaza is a public space focusing on a specific group of ENGAGE users. See the sections below for more information. ### Central plaza A meeting place for new visitors and a central hub to all other plazas.

### Enterprise plaza An hub designed for business-focused networking on a global scale and access point to corporate partner metaworlds.

### Education plaza Home to some of the world's best educators and universities. The education plaza is a place to learn, teach, and collaborate.

### Creative plaza Designed and curated by some of the world's most creative immersive artists and engineers. The creative plaza provides an opportunity to explore unique metaworlds and attend art exhibitions.

--- # 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.engagevr.io/engage/engage-link/engage-link-plazas.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.