
Why can a Rust player still use a plugin after leaving a group?
Removing a player from a helper group can leave another grant in place. Start with one player and one action, then trace where the permission comes from before editing any other player's access.
Use the action to find the permission
Read the plugin's current help and note the exact grant for the action you want to remove. Test with an ordinary account on a private world. If you use staff authority for the test, the plugin may have a separate administrator bypass. Check the plugin's own documentation for that behavior.
Work through the remaining access
Inspect the user and group permissions with your framework's read controls. Oxide allows permissions to be assigned directly and acquired from more than one group.
| What you see | What to inspect next |
|---|---|
| The user has the permission directly | Check why that grant was made. On the test copy, remove that grant alone and retry the action. |
| The user belongs to an additional group | Check that group's grants and its parent. Change the player's membership on the test copy only if the other access it provides should end too. |
| The default group grants the permission | Compare with a regular account that never had the helper role. Changing the default grant affects every member of that group. |
| Your manual changes reappear | Check whether a separate Discord link, access sync or script still assigns them. Correct the source responsible for granting access. |
Prove the restriction is narrow
After adjusting the grant on the test copy, ask the affected account to retry the one action and a second action it should still be able to do. Have a tester who should retain access run the first action too. In a disposable Oxide and Carbon test, a direct grant and a group grant survived a restart while a revoked grant stayed revoked. Repeat your own denial after restart when persistence matters.