This week the R&D Team has been discussing our current approach to read and edit permissioning.
The upshot of our discussion is that we are thinking of embedding the read capability with the edit capability. This would mean if you are given edit permission to something, you automatically get read permission to that same thing.
We think this makes life easier as when setting up/managing users you no longer have to remember to add two permissions in order to enable them to be able to see the configuration they are editing. It also removes a trap for new players who are likely to assume that the edit permission already comes with read capability.
The plain old read only permission would still remain for those cases where you want someone to be able to see but not edit a configuration.
If however you have a scenario where you are using the current edit permission in isolation (i.e. not coupled with the read permission) let me know via a comment on this post. Don't forget to include details as to why you've done this.
If it turns out that no-one is using the current edit permission in isolation then we will probably go ahead with changing its behaviour in the not too distant future.
