> For the complete documentation index, see [llms.txt](https://intellectualsites.gitbook.io/plotsquared/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intellectualsites.gitbook.io/plotsquared/features/plot-membership-tiers.md). # Plot membership tiers ## Introduction PlotSquared works with the following tiers of memberships to define the different behaviors / permissions / restrictions for Minecraft events, plot flags, commands etc. The member ties are one of the main part of PlotSquared by self. Plugins can check the membership tier for a player for a specific plot with the [PlotSquared API](/plotsquared/api/api-documentation.md). No configurations are needed to have memberships. ## Tiers ### Denied denied / banned players via `/p deny ...` * Cannot edit the plot * Cannot enter the plot ### Guest normal / non-added users * Cannot edit the plot * Can enter the plot ### Member added users via `/p add ...` * Can enter the plot * Can place / break blocks while the plot owner is online ### Trusted trusted users via `/p trust ...` * Can enter the plot * Can place / break blocks even if the plot owner is offline * Can use WorldEdit on the plot ### Owner plot owner via `/p auto`, `/p claim`, `/p setowner ...` or other * Has full control over the plot * Adding or removing users * Can place / break blocks * Use WorldEdit --- # 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://intellectualsites.gitbook.io/plotsquared/features/plot-membership-tiers.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.