From 834f8472dfd44f65ce36c52abfcbefe27ad5d6cb Mon Sep 17 00:00:00 2001 From: Cooldude2606 <25043174+Cooldude2606@users.noreply.github.com> Date: Sun, 22 Nov 2026 01:00:13 +0000 Subject: [PATCH] Clarify role permission warnings in documentation Rephrase warnings about role permissions for clarity. --- docs/managing-a-cluster.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/managing-a-cluster.md b/docs/managing-a-cluster.md index 1572d5f5..e79859d7 100644 --- a/docs/managing-a-cluster.md +++ b/docs/managing-a-cluster.md @@ -181,11 +181,10 @@ For example, a role for starting and stopping servers needs only `core.instance. Then add the role to the user under Roles on the page of the user. Use the Cluster Admin role for people who should have full control. -Be careful with what a role grants, some permissions give much more control than their name suggests. -The Roles page marks the permissions that stop, kill, delete, revoke or update things as dangerous. +Be careful with what a role grants, some permissions give much more control than their name first suggests. +The Roles page marks these permissions that can stop, kill, delete, revoke or update things as dangerous. For example `core.controller.stop` and `core.host.stop` shut down Clusterio on that computer, and it can only be started again by someone with access to the computer. -`core.user.update_roles` and `core.role.update` are not marked, but they are as powerful as Cluster Admin. -Setting roles has no restrictions, so a user who can do it can give themselves the Cluster Admin role. +Or `core.user.update_roles` and `core.role.update` which are as powerful as Cluster Admin because setting roles has no restrictions, so a user can give themselves the Cluster Admin role. The user can then log in as described in [Logging in](#logging-in).