Thanks to everyone for sharing their thoughts! We’ve started our work on this feature and we expect it to be available soon.

—AK

We are planning to add this functionality very soon, but there’s one fundamental thing we need to clarify with you first:

Current hardcoded labels in WordPress Toolkit are global/public. If server administrator sets a " demo " label on a customer’s site, this label will be seen by customer as well, since it’s just a property of a site in WPT. Moreover, the customer can change this label to a different one, for example, " staging ", and server administrator will see the " staging " label instead.

Adding custom labels means one of the following:

1. Custom labels stay public — in other words, everyone will see all labels added to a site, regardless of who’ve added them. So, server administrator could add a " pain in the ass " label to a client site, and the customer would see it and change the label to " no u ". We’re not particularly fond of this approach for obvious reasons.

2. Custom labels become “private” — in other words, only visible to users who’ve added them. So, a customer could add a label called " outdated " to their site, while server admin could add a label " insecure " to the same site, and they would only see the label they have added themselves. We like this approach better, but it might not cover cases like agency putting a particular label on a site for their customer (" production, don’t touch ").

So, the fundamental question we want to clarify is: do you prefer the first approach (“labels are public”) or the second (“labels are private”)? Which one better fits your use-cases? Please leave your opinion in the comments under this Uservoice request.

PS. Current hardcoded labels will be transformed into custom labels during the upgrade in both cases.

—AK

It’s pretty clear what scenarios are expected to be covered by custom labels. We’ll look into extending the labels functionality in the next WPT releases.

—AK