TheNextLvlPermissions
Portal command and entry permissions
Edit on GitHubPermissions
Portals uses a fine-grained permission system for command access and portal entry control. Command permissions follow a consistent pattern, while entry permissions are custom per-portal.
Command Permissions
Command permissions control who can use portal management commands.
All command permissions follow the pattern: portals.command.<subcommand>
Permission List
| Command | Permission | Description |
|---|---|---|
/portal action | portals.command.action | Set portal actions |
/portal cooldown | portals.command.cooldown | Set portal cooldowns |
/portal cost | portals.command.cost | Set portal entry fees |
/portal create | portals.command.create | Create new portals |
/portal debug paste | portals.command.debug.paste | Upload a debug paste |
/portal debug verbose | portals.command.debug.verbose | Toggle debug output |
/portal delete | portals.command.delete | Delete existing portals |
/portal list | portals.command.list | List all portals |
/portal notification list | portals.command.notification list | List notifications |
/portal notification remove | portals.command.notification remove | Remove notifications |
/portal notification set | portals.command.notification set | Set notifications |
/portal permission | portals.command.permission | Set entry permissions |
/portal redefine | portals.command.redefine | Redefine portal bounds |
/portal teleport | portals.command.teleport | Teleport to portals |
/portal warmup | portals.command.warmup | Set portal warmup delays |
The portals.command.action permission grants access to all action types.
There are no separate permissions for individual actions (teleport, connect, transfer, etc.).
The portals.command.notification.set permission grants access to all notification types.
There are no separate permissions for individual notification types (message, title, sound, etc.).
Last updated on