Profile-based scanner configuration: "Available with Ultimate" indicator placement is misleading
## Problem The current UI for the profile-based scanner configuration page displays an "available with Ultimate" upgrade callout or indicator under the **Scanner Health** column specifically. This placement is misleading because it implies that only the scanner health column/feature is gated behind the Ultimate plan, rather than communicating that **profile-based scanner configuration as a whole** is an Ultimate-only feature. As shown in the screenshot from https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/143066#note_3229458577, free-tier users see a teaser version of the security configuration page. The current placement of the upgrade callout under the scanner health column creates a false impression that: - The rest of the profile-based scanner configuration UI is accessible on free/lower tiers - Only the scanner health sub-feature requires an Ultimate license ### References - original design: [`Security_configuration_-_project-level_-_free_premium.png`](https://gitlab.com/gitlab-org/gitlab/-/work_items/586962/designs/Security_configuration_-_project-level_-_free_premium.png) ## Proposed Solution Move or update the "available with Ultimate" indicator so it clearly communicates that **profile-based scanner configuration as a whole** requires an Ultimate license. Options to consider: - Display the upgrade callout at the top of the page or as a page-level banner, rather than scoped to a single column - Add a clear page-level heading or notice such as: "Profile-based scanner configuration is available for Ultimate subscribers" - Ensure the teaser state of the page makes it unambiguous that the entire feature (not just scanner health) is behind the Ultimate plan ## Why This Matters Misleading placement of plan-gating indicators creates confusion for users and may undermine trust. Users should immediately understand the full scope of what requires an upgrade, rather than discovering limitations piecemeal as they interact with individual UI elements. ## References - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/143066#note_3229458577 - Screenshot showing current behavior
issue