Review privacy before publishing a static Plan export

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

Plan's static HTML export is not protected by the live web interface's login system. Publishing exported files can therefore expose data that a limited web group could not normally see. Review the export as a separate publication, even when the live dashboard already has authentication.

Record the starting point

Read the export and web-permissions documentation for the installed release. Decide which statistics may be public and whether player-identifying details should be included. Prepare a private destination for inspection rather than exporting directly into a publicly served website folder.

Work through the change

Generate a small trial export using the documented controls. Keep the files in restricted storage and inspect the available pages before sharing a URL.
Check player details, links and embedded data, not only the landing page. A hidden navigation item is not an access-control boundary for a static file.
Choose an export scope suitable for publication or keep the export private. If a website access-control layer is needed, arrange it deliberately with support; Plan web groups do not automatically protect copied files.
Test the intended destination from a signed-out browser. Confirm that public users receive only the approved material and that private files are not reachable by a direct URL.

Check the result

The publication should contain only the information you intended to disclose. Record the export date and scope because a static snapshot will not update like the live dashboard. Keep a list of published files so they can be removed consistently later.

If the result differs

If private details appear, pause publication and remove the trial files from the public destination. Review caches and any other copies before declaring exposure resolved. Do not turn off authentication on the live interface to make its behaviour match an export.

Return to the private authenticated dashboard if a suitable public export cannot be prepared. Preserve the analytics database and remove only the generated publication files. Notify the responsible administrator if player-identifying information was exposed.

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