google / google/site-kit-wp

Allow the Key Metrics and Audience Segmentation widgets to be hidden for view-only users

Open
#8,243 2 comments 0 reactions 0 assignees View on GitHub
Module: AdSense Module: Analytics Module: Search Console Type: Enhancement
Dominant language
JavaScript
Stars
1.4k
Forks
383
Avg merge
4d 12h
Merged PRs (30d)
80

Description

## Feature Description

At present, the Key Metrics widget can be hidden for an individual admin user by toggling a switch in Settings. However, view-only users don't have access to Settings, so cannot hide the widget.

The first iteration of Audience Segmentation will take the same approach.

We need to determine a mechanism that allows the widgets to be hidden for view-only users and apply it to both features.

One possibility could be to provide a cut down Settings area for view-only users which only has these switches (and perhaps some read-only visibility of other settings that the view-only user can see).

However, we could take another route for example changing the flow to allow an admin to override the view-only settings.

---------------

_Do not alter or remove anything below. The following sections will be managed by moderators only._

## Acceptance criteria

*

## Implementation Brief

* [ ]

### Test Coverage

*

## QA Brief

*

## Changelog entry

*

Contributor guide

Open the contributing guide

Research direction

Start by examining the existing Key Metrics hide control and the planned Audience Segmentation visibility flow, then trace how view-only users reach widget settings. Compare a view-only settings area with admin overrides; done when both widgets can be hidden by view-only users and the behavior is covered by the relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, wordpress
Domain
authorization, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.