The plugin was renamed and its main file changed, so WordPress deactivates it on update. Reactivate it once. Your saved capabilities are kept.<\/p>","1.1.0":"
The settings screen moved to Forms \u2192 Settings \u2192 Role Access. Capabilities that can escalate to administrator access are now flagged.<\/p>","1.0.1":"
Now installs on PHP 7.0 and later. No functional change on PHP 8.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The Role Permissions settings screen, with core capabilities grouped by area.","2":"Add-on capabilities, detected from the add-ons active on the site."}},"plugin_section":[],"plugin_tags":[1913,1332,1655,895,1915],"plugin_category":[46,54,58],"plugin_contributors":[232368],"plugin_business_model":[],"class_list":["post-386959","plugin","type-plugin","status-publish","hentry","plugin_tags-capabilities","plugin_tags-editor","plugin_tags-gravity-forms","plugin_tags-permissions","plugin_tags-roles","plugin_category-editor-and-writing","plugin_category-security-and-spam-protection","plugin_category-user-management","plugin_contributors-resonanzdigital","plugin_committers-resonanzdigital"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/resonanz-user-role-permissions-for-gravity-forms.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Disclaimer:<\/strong> This plugin is not affiliated with, endorsed by, or sponsored by Rocketgenius, Inc. Gravity Forms is a trademark of Rocketgenius, Inc. This plugin is an independent third-party extension.<\/p>\n\n Out of the box, only Administrators can use Gravity Forms. That is usually wrong for real sites: the person who writes the content is often the same person who should build the contact form and read the submissions, but handing them an admin account to do it is a bad trade.<\/p>\n\n This plugin gives the Editor role access to Gravity Forms, and lets you decide precisely how much.<\/p>\n\n On activation it grants a sensible starting set: Editors can build, preview and delete forms, and view, edit, export and annotate entries. It does not grant anything that changes site configuration, and it does not grant entry deletion. From there, a single settings screen under Forms \u2192 Settings \u2192 Role Permissions<\/strong> turns each individual capability on or off with a checkbox.<\/p>\n\n Add-ons register their own capabilities, and those are usually the ones that trip people up: the Editor can reach the form editor but the add-on's settings tab is invisible, with no obvious reason why.<\/p>\n\n This plugin reads the active add-ons directly from Gravity Forms and lists their capabilities in their own sections, using the add-on's own labels. Nothing is hard-coded. New add-ons, and third-party ones, show up without an update to this plugin, and add-ons you do not have are never shown.<\/p>\n\n Some capabilities can be turned into full administrator access by the person you grant them to. This plugin does not offer those capabilities at all. The settings screen lists each one with an info line instead of a checkbox, explaining that it is disabled because of the privilege escalation risk. That way it is clear the capability was considered, not overlooked. If the Editor role already holds one because other code granted it, the screen says so, so you can remove it there.<\/p>\n\n If you maintain your own list, the The plugin records which capabilities it granted. When you uninstall it, only those are removed. Capabilities the Editor role already had: from custom code, a role editor, or another plugin, are left exactly as they were.<\/p>\n\n Deactivating changes nothing at all. Your configuration is still there when you switch it back on.<\/p>\n\n\n Not in this version. Version 1 manages the Editor role only, which covers the large majority of sites that need this. Support for other roles is planned.<\/p><\/dd>\n It grants Check whether \"Full access\" is on. It overrides everything. Also check whether the user has more than one role, or whether another plugin grants the capability. Removing it here only affects the Editor role.<\/p><\/dd>\n No. It only adds and removes capabilities on the Editor role using the standard WordPress roles API. Gravity Forms itself is untouched.<\/p><\/dd>\nAdd-on capabilities are detected automatically<\/h4>\n\n
Capabilities that can escalate to administrator<\/h4>\n\n
gravityforms_user_registration<\/code> is the clear case: it allows editing User Registration feeds, and those feeds assign WordPress roles, so anyone who holds it can make themselves an administrator.<\/p>\n\nresonanz_user_role_permissions_gf_blocked_caps<\/code> filter lets you add to it. The built-in entries cannot be removed through the filter.<\/p>\n\nCareful with your existing setup<\/h4>\n\n
\n
Does this work with roles other than Editor?<\/h3><\/dt>\n
What is the \"Full access\" checkbox?<\/h3><\/dt>\n
gform_full_access<\/code>, Gravity Forms' catch-all capability. It overrides every individual permission, including capabilities added by add-ons you install later. It is there because it is occasionally what you want, and because sites migrating from a code snippet often already have it. For most sites the checkboxes are the better choice.<\/p><\/dd>\nI unchecked a box but the user still has access.<\/h3><\/dt>\n
Does this modify Gravity Forms?<\/h3><\/dt>\n
Where can I find further help?<\/h3><\/dt>\n