You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the only user of multiple sites, actually a mutisite instance, and even I don't do my normal day-to-day edits as an Administrator. My normal account is an Editor. This plugin should have a the ability to set which roles can pull and publish content independently of the plugin configuration settings. As it is I don't see any capabilities define to even assign to existing roles. Perhaps that would be the first step is to add capabilities that someone could assign via a role management plugin.
The text was updated successfully, but these errors were encountered:
timnolte
changed the title
Only Usable via Site Administrator, No
Only Usable via Site Administrator and No Capabilities to Assign
Feb 28, 2018
Looks like the Distributor Admin Toolbar option is there as a non-admin user, which is good. But I still think we need more feature capabilities that can be assigned to roles.
timnolte
changed the title
Only Usable via Site Administrator and No Capabilities to Assign
Only Usable via Site Admin and No Capabilities to Assign to Roles
Jul 2, 2018
It would also be nice, if you could assign non-admin user roles to have access to the to Distributor menu on the left, where you can pull content. Because it seems sometimes that content is waiting there to be pulled instead of being visible right away.
I'm the only user of multiple sites, actually a mutisite instance, and even I don't do my normal day-to-day edits as an Administrator. My normal account is an Editor. This plugin should have a the ability to set which roles can pull and publish content independently of the plugin configuration settings. As it is I don't see any capabilities define to even assign to existing roles. Perhaps that would be the first step is to add capabilities that someone could assign via a role management plugin.
The text was updated successfully, but these errors were encountered: