User Interface (UI) / User Experience (UX) · Access management (subscribers/authors) · Created by
Imper1um
closed
permissions workflow review
What functionality is missing? What is unsatisfying with the current situation?
Worldsmiths with the capability of creating advanced Access controls have to manually set permission groups for new elements created. The problem is that if you are creating a massive WorldAnvil with permission groups that allow for certain people to see the content based on Permission groups, you have to set that for every article you create.
What I am suggesting is that, with Private Defaults, you can, in your Access Rights Management, are able to setup a default Private profile. When you select Private with any new item (Article, Timeline, etc.), or make a Public item Private, it will automatically set the Permission Groups to the default.
A secondary (but certainly not required), is a way to create permission profiles that you could see those Permission Profile in the Private/Public dropdown on creating an article, or editing an item's permission settings.
How does this feature request address the current situation?
What this does is it just eliminates a few clicks from my normal process, but it also does have the opportunity (with Permission Profiles) to create a "workflow" for items.
What are other uses for this feature request?
What this can do is create an easy "workflow" for multiple author WorldAnvils, or make it easier for Worldsmiths that are process-oriented. For example, they could create a Permission Profile "In Progress" which only shows it to themselves, then a Permission Profile "In Review" which shows it to other authors and the content review team, then a Permission Profile "Spoilers" which shows it to any Spoiler groups. Perhaps Permission Profiles can also set the WIP/Draft settings of the Item as well.
The Team's Response
Thanks for your suggestions! Default subscriber groups are already supported: when creating or editing a subscriber group, find the "Default" checkbox (it's the bottom option). As for the permission profiles, we feel it's a good and useful idea, but there not enough community support for the dev time this would require. Feel free to suggest again in the future with clearer usecases and you might get more support, in which case we might reconsider!
Current score
10/300 Votes · +2302 points