Custom Tabs Visibility for all Users

That's a tough one, Monique, I took a look at the API explorer and the API, but was unable to deduce where the Custom Tab information is stored (let alone how to report on it), and also suspect that where ever "it" is, the New Experience Layout Templates will also be different. Barring a gem from Workfront Dev pointing you in the right direction, my suggestion would be to control the explosion: pick a Layout Template to upgrade run a report of those who use it email those user to schedule the upgrade, explain (with pictures) what will happen to any personalized custom tabs they've created give them some time to take their own inventory and/or provide a solid reason to defer the upgrade (e.g. 2 days?) perform the upgrade give them some time to report any oh-dang-that-DID-affect-me situations (e.g. 1 day?) rinse and repeat for each of the other Layout Templates, adjusting your affected audience size and warning/aftermath timing as need be Regards, Doug Doug Den Hoed - AtAppStore

Thanks, Doug that's what I was afraid of and actually that was my contingency plan, barring that leadership is ok with me putting the accountability on the masses to notify us before and afterward. It's a weird line that we walk, sometimes we hold hands way too much, other times we make users accountable. Monique Evans Stanley Black & Decker, Inc.

Ah! Thought of a Plan B, Monique: On a Monday (following the weekend refresh) apply ALL the new layout templates at once, in preview Explain the Custom Tab risk to ALL users at once, what preview is, that you've prepped preview, invite them to do their own side by side comparisons, and to create a special Workfront request (which you'd set up, in PROD) with a screenshot and description each discrepancy; AND (for hopefully the majority) "my stuff all looks good!" Issue to confirm they've done their part and are happy (consider giving out a trip to LEAP in a draw among the individuals who participate on these) Also share a public url link with them to a Workfront chart ( which you'd set up, in PROD) so ALL users can monitor (only) those issues (eg column chart by Entry Day, stacked by Issue Status) Resolve the Issues as they come in (either by teaching, and/or improving the new Layout Templates), building interest, confidence, and trust throughout the week On Friday, announce the results: either Go or No Go on Friday evening in PROD If Go, do so, Friday Keep the requests coming that first week Announce the LEAP draw winner the following Friday The "B" stands for "bold". Whaddaya think? Regards, Doug Doug Den Hoed - AtAppStore