A spicy question/suggestion I'm sure because permissions are tricky to design from a product perspective: But have you ever considered a role that is just verifier vs. author?
The problem this would potentially solve for our use case: We have tons of SME that know more about the product than I do, so we've opened up authoring to anyone in our team that takes a course on best practices. However, allowing author access also allows them to do things like rename boards, move boards, etc. - information architecture admin stuff that they really should not be doing and don't know the full impact of what their changes do to the rest of the collection.
I would love to be able to have a role that is able to verify and probably also edit on a card level - maybe not even the ability to create new content - something between end user and author. Just a thought!
Page 1 / 1
Agreed. I have a similar use-case as you - I want my SMEs to just be able to create and edit their own content, and not be able to create/edit anywhere else, or have admin powers like you described!
That would be awesome!
I wonder if that is actually possible. Since you could in theory set the authors of a collection then set board level access
I wonder if that is actually possible. Since you could in theory set the authors of a collection then set board level access
More granular permissions is something I dream about. Like, let someone be an author but not send Knowledge Alerts. Or prevent them from creating new tags or from moving boards around. Pls
This… Not let them create new tags… would be phenomenal… sounds like RBAC is needed (role based access controls) with fine-grained permissions.
Can we upvote this 500 times? 
The following idea has been merged into this idea:
All the votes have been transferred into this idea.
All the votes have been transferred into this idea.
We definitely need this, while we encourage people to help us keep information updated and include as much detail as possible - we need to gate keep who can verify that those edits. We do not trust all the people who edit our process and policy cards to verify that is what is current state and can/should be the process and policy. We also don’t want authors to be able to set themselves as the verifier - we need at least one other person’s eyes on a card before it is published or verified.
If I could add a suggestion here, we have some collections open to everyone to author, but it would be ideal to limit some of the actions only to a higher-level role (maybe the verifier groups within or collection owner). This would include things like creating new tags, archiving cards, reorganizing folders/cards.
Hey folks! Yesterday we released a number of changes to Permissions, including Custom Roles that allow you to create specific roles for authoring vs verifying! You can read more about it in the release notes here
Open→Complete
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.