The Permissions System

Thanks for all the awesome feedback on the permission system! I read all of your comments, designed a system, and have implemented probably about 60-70% of it at this point. 

I combined a lot of what the comments were saying and I'm pretty happy with it. Permissions can be edited on a per resource basis, and can be edited in the scope of "Roles", or "User Groups", that can be assigned to your users, and can also be specifically overridden per user. When access hasn't been specifically designated, it falls back to a default set on the world itself, either "Can Read" or "No Access".

This is somewhat complex, so I also want to make sure LK ships with presets that makes managing these intuitive for those who don't need it to be this granular. Maybe default groups like "Admins", "DMs", "Players", etc. Regardless, I think the way it's implemented makes almost every imaginable access setup possible. 

For example, if you are a DM and have invited your players to your world, you can set the Unspecified default to "No Access", create a Role called "Party Members", assign your players to that role, and then set their starting town permissions to: "Party Members: Can Read". Now they can see the town on the world map, and drill down into the town map. 

Perhaps there's a thieves' guild hideout in town that only the party's rogue, Josephine, knows about: You can set the hideout's permissions to "Party Members: No Access" and "Josephine: Can Read". Josephine will see a map marker on her town map for the Hideout, and her fellow party members will be none the wiser.

 Let's say your players run a tavern in town: Set the tavern to "Party Members: Can Edit", and your players can edit the Tavern article to their heart's content.

This is just per resource permissions, there's also per world permissions, like "Can create elements", "can upload images", etc. I haven't tackled hiding things within documents. Certainly possible, but I'm taking things a step at a time.

Don't mind the dev design :P

- Braden