Give a WorldGuard plot member access without making them its owner
A region member can receive ordinary access without being granted the owner’s region-management powers. Confirm the intended role before adding someone to a shared build.
Follow the procedure
- Stand in the correct world and inspect the plot with
/rg info REGION. Record its owners, members, bounds and parent before changing the domain. - Confirm the invited player’s exact identity and the plot owner’s authorization. Check whether the player already belongs through a group entry or inherited parent membership.
- Use the documented
/rg addmember REGION PLAYERcommand for ordinary plot membership. Do not use addowner merely because the member cannot perform one unrelated action. - Have the invited non-operator player test an approved build action inside the plot and attempt the same action outside it. Keep the trial away from valuable blocks.
- Check whether region management commands remain denied to the member under your permission policy. Membership and the server’s command permissions are separate controls.
- Inspect the region again and record the new member. If the invitation is temporary, schedule a documented review rather than assuming region membership expires automatically.
Check the result
The invited player should receive the intended plot access while remaining unable to manage region ownership unless separately authorized. Verify both inside and outside behaviour. An owner account’s successful test cannot establish that the member role is limited correctly.
If the result is wrong
If access remains denied, inspect relevant flags, parent membership and other protection plugins before changing ownership. Remove only the newly added member if the invitation was mistaken. Do not remove all domain entries or raise region priority to fix an unidentified permission issue.