Permissions issue

Thanks for the issue.

I am not sure what the best approach would be:

1. Show the button but instead of rendering the plugin configuration form show an 'access denied message'?
2. Not show the button at all
3. Should we have a seperate permission in the first place? In the end adding the button to the filter, which has it's own permission, should be good enough? I suggest removing the permission in the version 2 altogether.

What do you think?

I'd say it is better to keep the permission and not show button if no permission.
+ with permissions, you can limit access to certain controllers or settings (if needed). This way it is future-proof.

That being said, show button but show access denied message will enhance communication between clients and developers. Instead of finding out later, they quickly see what the problem is. Your decision to take :D