Hubs Permission List (pending)

Hub level permissions

• Manage hub - A
• Manage categories - A
• Manage rooms - A
• Manage roles - A
• Mute users - B
• Create invites - A

Category level permissions

• List rooms - A

Category & Room level permissions

• Spawn media - B
• Spawn camera/take photos - B
• Spawn drawing - B
• Upload files - A
• Pin/unpin my objects - A
• Pin/unpin any object - A
• Remove any objects - B
• Control any pinned objects (Video player, pagination) - B
• Manipulate any pinned objects (Move/Rotate/Scale) - B
• Send chat messages - A
• Enter room (spawn avatar, create outgoing data channel) - A, B, C
• View room (join janus server) - C
• Manage room - A
• Kick users - C
• Ban users - C, A

Kicking & muting of users is always allowed by the creator of a room.

---

Mechanisms

• A - API operations or Hub channel operation gate
• B - Reticulum NAF packet component filtering
• C - Signed Janus connection token + Janus API

--

• rooms you create from hubs.mozilla.com do not belong to a hub. anyone can join them with the link. same as now.
• rooms that don't belong to a hub can be moved into a hub by anyone who has permission to do so. Once it’s in a hub it can’t be moved to another one.
• there is no security model applied to a room if its not in a hub, and if its in a hub, the hub's security model is applied. (there is no longer the concept of a 'room owner')
• once a room is in a hub, you have to be logged in to load the page. (when a room is moved into a hub we'll just force everyone to refresh. most of the time there won't be many people in there)
• rooms in a hub can be listed or unlisted. unlisted rooms do not show up in the hub page but can be shared as usual via the private link, but have the security model of the hub applied. (like a private channel in slack)
• a room can also be created directly from a hub page
• anyone can change the name of a room that’s not in a hub. If the room is in a hub then the security model determines who can change the name.