
Set up Oxide group inheritance for junior and senior staff
Put the permissions both staff levels need in a common parent group. Give more sensitive permissions only to the senior group. Oxide's child groups inherit every permission from their parent.
Draw the relationship before adding permissions
Suppose both groups need to read moderation reports and only leads should resolve them. Make a reports group with the read grant, then make leads its child. The leads group adds the resolve grant from the plugin's documentation. A player who should only read reports belongs to reports.
In the Oxide server console, the parent relationship in this example is oxide.group parent leads reports. Read the current groups before applying that relationship if you already have a team setup. A group's title and rank are separate settings from its parent.
Prove both sides of the boundary
Use one test member in each group and check the read action on both. Try the resolve action on a test report and verify that only leads can do it. Use regular test accounts without separate grants or native Rust admin status.
If a junior test account can resolve, start with oxide.show user followed by its identifier. Look for a direct grant, another group membership or an unexpectedly broad grant in a parent group before changing everyone else's permissions.