To give a player access to a specific command, first identify whether your server is Java or Bedrock and what software it runs. On a Java server using Paper, find the command’s exact permission node and assign it with a compatible permissions plugin such as LuckPerms. On a Bedrock dedicated server, Microsoft documents an owner-level /permission workflow. These methods are different; neither should be assumed to work on Realms or an unspecified hosting setup.
First identify your server edition and software
Permission commands and plugins depend on the server platform. Confirm whether you run Java or Bedrock, then check the server software shown by its host or in its server files. LuckPerms supports several platforms, including Bukkit, Spigot, Paper, Fabric, Forge, NeoForge, Nukkit, and Velocity, but compatibility and installation vary. Its installation guide recommends Paper for a non-modded Java server and Nukkit for a Bedrock server. See the LuckPerms site and its installation guide before installing it.
Java server: grant one command with Paper and LuckPerms
If your Java server runs Paper, use Paper’s permission reference to find the exact node for a built-in command. Then use LuckPerms to grant that node to the intended player or a group. This allows selective access without making the player an operator.
1. Find the exact permission node
Look up the command in Paper’s permissions reference, which covers built-in vanilla, Bukkit, and Paper permissions and indicates whether players receive each by default. For example, Paper lists minecraft.command.give as unavailable to players by default. Do not guess a node from a command name: the actual permission string must match the relevant documentation.
For a command added by a third-party plugin, check that plugin’s own documentation. Paper’s reference does not establish every plugin’s permission nodes or defaults.
2. Assign the node in LuckPerms
LuckPerms represents permissions as nodes whose values can be true, false, or undefined. Its documented usage supports assigning nodes to users or groups and applying contexts, such as a particular server or world. Use the command syntax and target selector in the LuckPerms usage guide for your setup, replacing the example node with the one you verified.
Rank #2
- Upgraded Two Zipper Pockets: Forvencer server books feature two secure zipper pockets for better organization of coins, cash, and receipts, ensuring that everything you collect has a safe and secure place
- Smart Storage & Quick Access: Designed with 8 multi-functional compartments, the right side includes a guest receipt pad, while the left has a money pocket, ticket pocket, and credit card slot. Two small clear pockets store bills, receipts, and other visible items. A stitched pen loop ensures you always have your favorite pen ready
- High-quality & Easy to Clean: Crafted from high-quality PU leather with heavy-duty stitching, this server book is built to last. It resists tears, scratches, and its waterproof surface makes cleaning easy with just a damp cloth or a non-chlorine sanitizer
- Perfect Fit for Your Apron: Measuring 5” x 8”, this compact organizer is slightly smaller than other models, making it ideal for bending or sitting while carrying in your server apron. It holds everything a waitress needs—a place for everything
- What's Included: This server organizer comes with multiple open and zippered pockets to store money, receipts, tips, etc. Clear sleeves are perfect for keeping menus or special lists while serving. Available in a variety of colors, allowing you to express yourself even when in uniform
For a one-player grant, assign the node to that player. If several players need the same access, assign it to a group and place the relevant players in that group. Contexts can scope a permission to a server or world where appropriate.
3. Keep LuckPerms administration separate from player access
LuckPerms’ first-use instructions show granting an account access to LuckPerms commands from the server console with lp user <your username> permission set luckperms.* true. That is an initial plugin-administration example, not the way to give an ordinary player one Minecraft command: luckperms.* grants broad access to LuckPerms itself. Use the console as directed by the guide to establish plugin administration, then grant players only the verified command node they need.
Rank #3
- 【All-Purpose Server Guest Book】Ideal for busy waiters and waitresses this server book for women and men helps you stay organized on the job with 7 large pockets that can store cash, checks, tips, bills, receipts, coins, bank cards, and more. Differ from middle holder, side pen holder avoid annoying ink stains.
- 【Perfect Size】 The size of this serving book: 7.5inch * 5inch, the expansion size: 10.2inch * 5inch.It is a moderate size fit many restaurant server apron pocket. (Noted: apron & guest check are not included).
- 【Premium Material】This waitress book organizer made by high quality PU leather.It touch soft and comfortable. This material is waterproof and easy to clean, you can easily remove surface stains with a wet cloth.
- 【Humanized design】Get this server book to streamline steps of service. It is simple, practical, elegant and necessary for any restaurant-like establishment. The money pocket on the left can also put the guest check pad, so that left-handed people can easily use it.
- 【Outside of Work】This server wallet has a cute appearance,you can take it for travel ,school ,shopping and so on. Artistic waitress book highlight your unique taste. Unique design server book show your outstanding, easily impressed people at a glance.
Bedrock dedicated server: use the documented permission workflow
For a Bedrock dedicated server, Microsoft documents the /permission <action> command. It is an owner-level command and requires cheats; it is not Java Paper or LuckPerms syntax. Microsoft’s Bedrock dedicated-server command reference documents these actions:
/permission listlists current player permissions./permission setsets permissions./permission reloadreloads the permissions file from disk and applies its permissions.
Consult Microsoft’s reference for the precise arguments and permissions-file format for your server. This documented workflow is specifically for Bedrock dedicated servers; do not apply it to Java servers, Realms, or other hosting products without documentation for that environment.
Choose the approach that matches the access you want
| Your situation | What to do |
|---|---|
| One player needs one Java command | Verify the command node in the relevant documentation, then assign only that node to the player with a compatible permissions plugin. |
| Several Java players need the same commands | Use a group in a compatible permissions plugin and grant the verified node to that group. |
| A permission should apply only in a particular server or world | Use a permissions context if your plugin and setup support the intended scope. |
| The command comes from a third-party plugin | Find its node in that plugin’s documentation; Paper’s reference does not cover every plugin. |
| You run a Bedrock dedicated server | Follow Microsoft’s owner-level, cheats-required /permission and permissions-file instructions. |
Operator access is broader than a single command grant. If the goal is limited access, verify the command’s node and grant that node rather than making the player an operator. Exact nodes and behavior depend on server version, installed plugins, and the permission defaults documented for them.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
