Feature request: allow filtering of user capability required for controller access and actions #367
Description
Currently, I believe manage_options is hardcoded as the capability required to do anything in Fluent SMTP.
It would be nice to add a filter so this can be customized. Further, it would be nice to have the context on what action is being verified passed to the verify() method in the base controller class, and then include that in the filter, so that use of the filter could include logic about capability required based on target action.
An example use case for this is that we'd like a store support person to have the ability to view email logs, but not the capability to change Fluent SMTP settings, view connection info, etc.
Thanks for considering it!