Permissions

There are four nodes, and all of them default to operator.

Permission	Grants
soma.hider.admin	Create and delete zones. Includes the three below.
soma.hider.operate	Start, stop and inspect zones, and capture chat triggers.
soma.hider.reload	Reload the configuration files.
soma.hider.bypass	Use /sh bypass to see real identities inside zones.

soma.hider.admin is a parent node, so granting it also grants the other three:

Role	Give them	Why
Whoever builds the events	soma.hider.admin	Defining and deleting zones is a configuration job, and they will need to reload after editing files.
Staff running events on the night	soma.hider.operate	They start, stop and check zones without being able to change the definitions.
Moderators	soma.hider.bypass	They need to see who is really who to handle a report mid-event.

This is the node worth thinking about twice. A player holding it sees through every zone, everywhere, as soon as they toggle it on.

That is exactly what a moderator needs, and exactly what a competitor must never have. It sits outside operate on purpose, so you can hand out one without the other: an event host can run your zones without being able to see through them.

The toggle state is saved per player, so someone who turned it on last week still has it on today.