> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/product/moderation.md). # Moderation Insights about our moderation policy and actions taken Open Collective provides some tools to make sure that disrespectful users and abusive contents don't have their place in your community. The moderation is done based on our [Community Guidelines](https://docs.opencollective.com/help/about/community-guidelines). Especially, these types of contents are never welcome on the website: * Spam or unwanted commercial content * Abusive or inappropriate language * Irrelevant or erroneous content ## How to report abusive content Please send all your reports for spam and abusive content [here](https://opencollective.com/contact). ## Limited user account Limiting user's account is currently our main tool to prevent activity from malicious users. We usually limit an account after spotting one or multiple attempts at spamming or doing malicious things. When you're account is limited you'll be unable to complete any sensitive action on the website, including: * Create/edit expenses * Make financial contributions * Create conversations If your account gets limited by mistake, you can [contact us](https://opencollective.com/contact). --- # 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.opencollective.com/help/product/moderation.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.