We're experimenting with Quire.io permission system and we have granted most of our team members the normal+ permission.
The main thing they're missing with that permission level, is the option to add a board to a project. The web interface does show the action, but it then reports "You do not have permission to perform this action".
Just like those users are able to add tasks/tags/..., I would have expected them to be able to add new boards as well (and perhaps not be able to delete those boards?).
I'm afraid he's thinking of something more like ACL based permissions.
I suggest you switch to ACL based to allow a more granular control, that way you could preserve some presets, but also let admins choose custom permissions (even save those custom as presets for future use). It could work like a check list.
Harley Cascante, Oct 12, 2018
Works like a charm now - thanks for fixing this! 👍
Gert Vanthienen, Oct 18, 2018
Hi Gert, Normal/Normal+ members should be able to add & manage boards now. 😃
Crystal, Oct 18, 2018
Hi Crystal,
We're just experimenting with quire.io at the moment and we're just a small team anyway, so giving everyone admin rights definitely works for us.
However, I still think it would make sense to allow people to perform a basic/non-destructive action like this in a project without having to grant them the karma delete entire projects/organisations.
Gert Vanthienen, Oct 12, 2018
Switching to ACL-based permissions would obviously allow for a lot more flexibility/configurability, but we do appreciate Quire's simple approach to permissions.
Gert Vanthienen, Oct 15, 2018
Hi Gert, We shall think about what you suggested. Have you considered giving your members the Admin role so they are able to add (and delete) boards?
Crystal, Oct 12, 2018
Well that's why I think they can keep the current permissions as presets, easy as they are, switch to ACL but leave the current presets available + add one option "Custom permissions" to let advanced users set their own specific set of permissions.
Remember, switching to ACL is more of an approach to accomplish the same task, but allowing more granularity when required, always being an option while having the simplicity of the current permissions still as the default presets.
It doesn't mean they will put a banner saying "Hey we switched to a more complex permission system, see if you are good enough to use it". They'll just switch to it code-wise but leave the frontend as it is now, adding 1 optional custom set of permissions for those who require so.
Harley Cascante, Oct 16, 2018