We are experiencing an undesirable behavior issue with Community Events and the default Subscriber role. Generally speaking, subscribers have no access to anything in the WordPress admin area except for the dashboard and their profile. Using Community Events, there are settings where you can allow users to edit and delete their own events. This is great when dealing with the front end interface, however these settings enable the admin area to now have access to see all events (though they can only edit their own), and add new ones through the admin area… a different and slightly more confusing environment for the end user.<\/p>\n
On top of this behavior… when checking the settings to NOT allow a user to add new venues and organizations, having the ability to edit their own events now bypasses this security feature if the user creates their event using the admin area interface instead of the front end interface. I am aware that I can “block” any role from accessing the admin area altogether… and even redirect them to a different URL if they attempt it. But in our case, we would like the subscriber to have access to the WP Admin area for profile purposes, and other potential purposes down the road.<\/p>\n
Typically this would not be an issue with roles that are already permitted to do such tasks… but for a subscriber I am unsure why this ability has occurred. Was this action done by default? Or is there anything else we can do to remedy this? The desired outcome would be for the Subscriber role to NOT be able to have access to any part of the Events Calendar in the WP Admin area, and only be able to access any features through the use of the community pages (add\/list). Any advice would be welcome.<\/p>\n","protected":false},"template":"","class_list":["post-1350803","topic","type-topic","status-closed","hentry"],"yoast_head":"\n