Give a staff member a limited Plan web group

Applies to: Plan; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

Plan's website has its own permission groups. A staff member who can view session summaries does not automatically need player-address information or full web administration. Configure the intended web access instead of granting a broad Minecraft permission wildcard.

Record the starting point

Read the web-permissions documentation for your installed Plan release. Decide exactly which pages the role should see and whether they contain player-identifying data. Ensure the web interface uses the documented HTTPS arrangement before enabling authenticated access.

Work through the change

Use Plan's documented web permission editor to inspect or create the intended group. Select permissions that match the staff task rather than copying the administrator group wholesale.
Follow the release's registration instructions and documented group assignment mechanism. Plan documents the plan.webgroup.{name} permission for registration-related group selection; confirm how it applies to an existing account before expecting a retroactive change.
Sign in with a dedicated test web account and open an allowed page. Then attempt one page or action the role should not access.
Remove any temporary broad permission used during testing and repeat the login. Keep a record of the final role and the person responsible for reviewing it.

Check the result

The account should see the intended analytics and be denied unrelated administration or private information. Test the actual web session, not only the player's Minecraft group. A menu link being hidden is insufficient if a direct URL remains accessible.

If the result differs

If access differs, compare registration-time group assignment, current web-account membership and the generated permission configuration. Do not disable web authentication to work around a group mistake. Check the installed release documentation before editing account records directly.

Restore the previous group permissions and revoke the trial account if the boundary is unclear. Keep the analytics database intact. Role testing does not require deleting player sessions or exposing the web port publicly without its existing access controls.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report