Not sure entirely how to explain this but it would be really cool if the "Collaborator" invite role entailed more personalisation and different types? of roles.

Best thing I can set as an example is Kanka. It has roles for members, "staff" of the project, and the Member role is customisable so you can choose to manually switch specific pages on/off for them to see. So they can interact with some parts of the project and not others - such as some private pages like secret lore - and other roles cannot.

Another example would be if a race is visible for patrons/players ONLY and other roles such as other members or public viewers can't/shouldn't be able to see it.

TLDR More customisable different roles to give people when inviting them into a project, if it's feasible.

What I am really missing is an option of permissions to not allow creation of new pages for non-admins

It would make my life INFINITELY more organized if I could edit perms on a per-tab basis. I thought this had already been suggested but I'm realizing it doesn't seem to be on here?

Ideally, tabs would default to inheriting the perms of the article as a whole, but in addition to the current functionality of being able to "hide" a tab from public view, I'd dearly love to be able to hide it from some users/roles while allowing viewing or even editing access to others.

Alternatively, I could also work just as easily with permissions being independently adjustable for specific elements--like having a zone you can add to any article and set perms for, allowing a user/role to view/edit within that zone only. If there's already a suggestion here for selectively-revealing "secret" element content, this would piggyback on that nicely I think. EDIT: I did just find the "Selectively reveal secrets" suggestion thread. I'm all for that, though I think this is still a standalone suggestion because I don't just want selective viewing perms, but also selective editing perms.

Surely I'm not the only one with this need!

More long-winded justification:

I use my LK project collaboratively with my players, but that's been less than ideal so far, because either something is a set-in-stone article that my players cannot edit, or I have to create a completely separate article that serves the exact same purpose as the first, except it additionally lets them write and edit things they wish. This is especially prevalent on articles meant to feature a player character, as I'll have the public-facing version and then a sub-article under it that is hidden to everyone except that character's player, who also has editing perms to the sub-article.

This is annoying because I can't consolidate information into a single, more intuitive article, which has a ripple effect of the efficiency/convenience of many other aspects of the app, and also it just... clutters up the directory in a way I dislike.

I want to really lean fully in to utilizing LK as a way for my players to organize and give a home to their lore stuff without me having to manually transcribe it for them, but while also still preserving those things as secrets between me and that player--so better flexibility in being more specific about what content can have unique permissions would be greatly utilized!