> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/general-information/accessing-and-using-the-logicnets-community-portal.md). # Accessing and Using the LogicNets Community Portal This is the Community Portal and you can access it directly at community.logicnets.com. You can also get to it from our website or when you click the Help icons and links in the Designer. Please complete the sign-in process the first time you access this community, so you can benefit from single sign-on and fully participate in the community. Feel free to "Like" our content, use "Reply To" to ask general questions about a topic, and "Follow" topics to receive email notification when we update that topic. We moderate all replies before making them public, but you can count on LogicNets seeing your posts and responding where appropriate within our normal support service levels. Once replies have been approved, they become part of the public portal available for others to see. They are also searchable through Google at that point. Remember to raise production problems or defects specific to your LogicNets account through your LogicNets Support Portal. --- # 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://community-test.logicnets.com/release-9/getting-started/general-information/accessing-and-using-the-logicnets-community-portal.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.