Permissions

PulseNode's single permission, and why the plugin has no player-facing nodes.

PulseNode v5.0.2Paper · Spigot1.21 – 1.21.x

PulseNode has one permission.

Permission	Default	Grants
`pulsenode.admin`	`op`	The `/pulsenode` command and all sub-commands

The permission is declared on the command itself, so a player without it does not see /pn in tab completion at all.

Why only one

PulseNode is an operator tool. There is nothing a normal player would do with it: the plugin collects metrics and posts them, and the only in-game surface is a status readout, a reload and a security GUI — all three of which are administration.

Everything else lives in the dashboard, where access is controlled by your account rather than by in-game permissions.

Granting it

BASH

lp group admin permission set pulsenode.admin true

Operators have it by default. If you run a server where staff are not opped — which is a good practice — grant it explicitly to the ranks that need it.

The security GUI shows IP addresses

/pn security lists failed logins and connection floods, which include IP addresses. Grant pulsenode.admin only to staff you would give server-log access to anyway.

Dashboard access

Account-level, not permission-level. Anyone who can sign in to your PulseNode account can see every server on it — there is no per-server role split inside a single account.

If several people need access to different servers, the clean separation is separate accounts, each with its own servers.

API access

Business plans can generate API tokens under Account → API. A token authorises reads against your own data through the public API and is independent of pulsenode.admin — one is an in-game permission, the other a web credential.

Rotate a token when somebody leaves, the same way you would rotate any other key.