1123 make limited yoast sidebar elements available to more user roles#23103
Conversation
Coverage Report for CI Build 171Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage at 50.018% (no base build to compare)Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
…ailable-to-more-user-roles
|
I haven't finished my CR/Acceptance test yet, but I want to raise an early flag for the decision of opening the Academy page to users that have no other access in Yoast pages, which can have its issues. For example, if you're an Author and visit the Academy page (which this PR makes now possible), you can eventually be greeted with the Schema Aggregation Endpoint modal: which leads you to a Yoast page that you have no access, thus getting a 403 page: We can safeguard this particular case, but I believe it's gonna be a matter of time until we get similar issues, so I would urge to double think whether we want to open up only a subsection of pages to new user roles. cc: @manuelaugustin |
…ore-user-roles' of github.com:Yoast/wordpress-seo into 1123-make-limited-yoast-sidebar-elements-available-to-more-user-roles
…ailable-to-more-user-roles
leonidasmi
left a comment
There was a problem hiding this comment.
CR: 🚧 I left some feedback on how to safeguard introductions to roles that just not got access to them.
Also another concern I have regarding the requirements and how we implement them:
I see that in the topbar, we moved the Academy menu item from the submenu level to the main menu level, which I am not sure it was what we wanted, so I would double check with Product.
To make the above point more clear, this is what we show to an admin in production:

and this is what we show to an admin with this PR:

If that was needed in order to be able to show the Academy link to users that dont have access to the SEO settings menu, then I think we should at least make it so that what admin see is the same with this PR and without (unless it's not an issue for Product)
…-limited-yoast-sidebar-elements-available-to-more-user-roles
…-wide Reverts the Introductions_Integration-level User_Can_Manage_Wpseo_Options_Conditional gate and moves the capability check into the should_show() of each introduction that links to a wpseo_manage_options-only destination. Addresses CR feedback that the blanket gate would also hide intros which should remain visible to lower-cap roles (e.g. Premium's AI_Optimize_Classic_Introduction). Gated this turn: - Schema_Aggregator_Announcement (CTA points at Settings, admin-only) - AI_Brand_Insights_Free_Trial - AI_Brand_Insights_Post_Launch Black_Friday_Announcement and Delayed_Premium_Upsell are intentionally left ungated as general promos. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The academy move was approved by product :) |
…ore-user-roles' of github.com:Yoast/wordpress-seo into 1123-make-limited-yoast-sidebar-elements-available-to-more-user-roles


Context
Summary
This PR can be summarized in the following changelog entry:
Relevant technical choices:
Test instructions
Test instructions for the acceptance test before the PR gets merged
This PR can be acceptance tested by following these steps:
Relevant test scenarios
Test instructions for QA when the code is in the RC
QA can test this PR by following these steps:
Impact check
This PR affects the following parts of the plugin, which may require extra testing:
wpseo_manage_optionscapability - quick smoke test neededOther environments
[shopify-seo], added test instructions for Shopify and attached theShopifylabel to this PR.[yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached theGoogle Docs Add-onlabel to this PR.Documentation
Quality assurance
grunt build:imagesand commited the results, if my PR introduces new images or SVGs.Innovation
innovationlabel.Fixes #