I'd recommend as part of these changes that we deprecate or repurpose Search-Console-access-request and either add a new tag or otherwise use the general-purpose SRE tag for these (you alls' preference!) . I also made up this form which ITS can use to make appropriate tickets in the future - feel free to update this form as appropriate

Hi @MGerlach -
Apologies for the confusion here!

Hm, I'm not sure that general-purpose QA flows will necessarily uncover potential breaking changes here. I also think teams and team-embedded QTE folks have more context on their features and can ensure that the appropriate user flows are being tested and validated.

Oops sorry, over-active bot!

As @Jdlrobson-WMF 's manager, provided he has filled out the above form I approve this request

As Seddon’s manager I approve this request

Hello - Can you add @HSwan-WMF , @DLin-WMF , @Maryana , @derenrich , and @etz as members of acl*Project-Admins ? These are members of the Future Audiences team that would like to organize their projects more granularly in the future. Thanks!

Closing as configuration changed - this access has been granted. Going forward ITS will be governing this process, we'll be posting more info about this in the next month or so.

Synced with @SSpalding-WMF about this async, sounds like this request is no longer relevant. We'll be moving to have ITS manage this process going forward in the next month or so, but in the meantime I can help if you or others need access. Thanks!

Hey @nshahquinn-wmf - granted just now -- we're still spinning up the ITS-mediated process for this, so I granted this manually for now. We'll post once we've gotten the ITS version ready to go!

Thanks for flagging this @bd808 ! My accounts were caught up in this, due to my name change.

This can be closed as config changed - we decided not to have a dedicated board for these back when this ticket was first created.

This can be closed now, as per our contact this feature has been removed.

Hi all -
Just now, as a one-off, we've granted access to Neil for en.wikipedia.org and en.m.wikipedia.org. Please let me know if there are any issues with this.

Resolved! We've updated our materials, conducted interviews, and passed on candidates to the final round. Thanks again to everyone involved in this process!

Hi @Scott_French - thanks for looking into this and the summary!

Hi @Scott_French - Thank you for taking a look at this!

1. Yes - this is a good summary. We can currently only see a subset of domains and properties, but I know there are many more out there, both for projects and language variants. If it's possible to generate such a comprehensive list of the full set of available properties and then add that full set to the console we would appreciate it!
2. Delegated ownership should be fine, thanks for checking on this. Though with the caveat that at present even Suman does not seem to have access to the full conceptual set of properties and domains.

Thanks again for helping out with this, happy to answer any further followups!

@Reedy - A good question! I've asked about this and will follow back up here when I hear more. I initially supposed the domain property percolated down but this appears not to be the case. I'll reply back when I get the full list and can update the form. Moving back to "In Progress" for now as I work through this.

Hello -
I have a few batch additions to suggest for the teams and projects I work with.

Thank you for filing. I've filled out the form just now for the wikipedia.org domain, on behalf of the WMF Web Team, as we typically monitor SEO-related issues and manage the search console. We should be good to go on this going forward, please flag if there are issues.

Tomorrow morning: @ovasileva to update spreadsheet, send to @jscherer who will create the form - @Jdlrobson will update the link in the survey. We will aim to have everything ready to go by Friday Nov 29, deploy on Monday Dec 2. We'll use this ticket for deployments.

For this experiment we chose to use session id ; closing with this in mind

QA was completed in the deploy task: https://phabricator.wikimedia.org/T378098

Dupe of T379241

Discussion to follow this week to further refine this ticket based on designs / follow up on https://phabricator.wikimedia.org/T378100 - based on the outcome of this, we should create a relevant spec and estimate between now and next sprint

The spec has been created on this already, work for this will be handled in https://phabricator.wikimedia.org/T379214