Thanks for the positive feedback and for your interesting question.
MLA is designed to be as “WordPress-like” as possible, and it uses the WP roles and responsibilities to implement permissions and restrictions along the same lines. For example, there are current_user_can() checks for reading and editing posts, assigning taxonomy terms, uploading files, managing options, etc. More specifically, a user must be able to upload_files in order to see the Media/Assistant admin screen. This is the same filter applied to the WordPress Media/Library admin screen. You can search the MLA code for calls to current_user_can to see all the current checks.
What users have access to is determined by their WordPress “role’. Subscribers and Contributors do not see any MLA admin features. Authors can access the Media/Assistant screen but cannot edit items or taxonomy terms and cannot access the Settings screen. Editors can, of course, edit things but cannot access the Settings screen.
MLA does not have any hooks of its own to further restrict access to its features. I would be happy to consider adding something along these lines if you can give me details about which MLA features should be limited.
I will leave this topic unresolved for now. Any additional information you can provide is welcome. Thanks for your interest in the plugin.
