Feature Request? maybe?

Hi Hube2!

1) You’ll be pleased to know that more robust Theme Editor tracking is already on our radar and will be released very soon. See GitHub issue #313 for more details on the progress of the feature.

2) For your second question, yes you can limit what Roles can access Stream by choosing allowed roles under Stream > Settings > General > Role Access.

However, we do have plans underway to allow you to be able to choose specific Users too, not just roles. That is being tracking in GitHub issue #253. You follow our progress there as well on that feature, we hope to release a solution soon (within the next few weeks.

Thanks for your feedback!

Cool, thanks, will be looking forward to it. I honestly don’t like the fact that I need to start monitoring what people are doing, especially site admins, but I guess it’s a necessary evil when you’ve got many sites to maintain and need to know who broke what.

Hey Hube2, I’ve just been thinking more about what you are wanting to achieve and I think I see the dilemma here you’re describing.

The purpose of roles is to grant permission to certain levels of access, it seems like in this situation that the roles are the same (you are both Administrators) yet the permission levels desired are not the same. So really, this should probably be achieved using different role assignments.

I think it would be wrong of Stream to decide that some Administrators can access the plugin and its settings, while other Administrators cannot. Instead, it might be better to create some kind of Super Editor role for your clients, where they essentially have all the power of an Administrator minus the ability to access Stream or create other Administrator users. This would seem to me to be the most pure way to solve the actual problem.

I would suggest taking a look at the Members plugin, which will give you the ability to do something like this.