Permissions are the forefront of what a user can use to protect themselves in a Session. They allow for Worlds to be set in whichever way you as a creator deem it so. For example, you could create a social world with no building, or even an "experience" world that will only allow you to interact with specific set pieces.
Roles
There are a handful of default roles in a world. Each role includes the capabilities of the last.
- Admin: Full administrative capabilities of the world and its users.
- Builder: Full editing permissions of the world.
- Moderator: Ability to kick, silence, respawn, and change the role of users.
- Guest: Ability to interact with the world and spawn items.
- Spectator: The base-level permissions, allowing you to use an avatar, move around and chat with people.
Tools and Moderation
Underneath the "Users" tab in the Session Menu is a list of actions you may perform depending on your role in the session. You may do things such as:
- Jump: Teleports you to the user's current position.
- Respawn: Completely resets a user and their avatar, as if they had just joined.
- Silence: Mutes the user for everyone in the session.
- Kick: Disconnect the user from the session, temporarily removing them.
- Ban: Kicks the user and disallows them from joining again.
Depending on your own permissions, you may also change other users' roles, as well as the default role for new players (depending on whether they're anonymous, registered, the host's contacts, or the host themself). This is done through the "Permissions" tab in the same menu.
Technical
Every new world comes with a default set of permissions under a slot named Roles, roughly organized by the respective role. Each of its child slots has a number of components from the Permissions category.
As of September 2025, there's no official way to check a player's permissions within ProtoFlux.[1] It's still possible to test for some of them based on their side effects; for example, Edit Mode permissions (by default given to the Builder role and above) can be tested for with the CanBeGrabbed node targeting a slot with the Developer tag.[2]