Highlight currently selected environment optically

[gerhard.schraml]

Hi,

I am pretty new to using environments for separating PROD and DEV requests. Is there a way to optically highlight the currently selected environment on top of spotting the selected value in the environment dropdown? I want to prevent myself from firing requests into the wrong environment.

Gerhard

[Kurmavatar (Subramanya Raj)]

Hi @gerhard.schraml

Welcome to the community

Clicking on “Quick look” next to your environment dropdown helps you identify values that are being sent across.

Based on your use-case, I would recommend creating two environments one named “Prod” and other “Dev” to distinguish them clearly. Refer to this resource here to know more : )

[gerhard.schraml]

Hi Raj,

thanks for your response. I already did exactly what you suggested - using two environments called “Prod” and “Dev”. My question is about user experience, not functionality. How can I clearly indicate by optical means a difference between the two environments - e.g. colored environment indicators in red and green or similiar, to prevent myself from accidentally sending requests to “Prod” environment when I should have sent it only to “Dev” environment.

See my “mockups” - not so crude, but with a similar warning effect.

KR,
Gerhard

[Kurmavatar (Subramanya Raj)]

@gerhard.schraml Yes, I understand this better now! Although we do not have this effect, we do have something similar to this. When you hover over the defined variables - there is an error message along with the color to display the difference.

Although, I totally agree your mentioned way makes it way easier to identify hence - would recommend you to raise the feature request on our Github Page from this link here. GitHub is the forum where our team picks up the issue and provide the resolution at earliest, that is how we keep track of the bugs/ feature requests for the application

[gerhard.schraml]

OK, here’s the feature request:

https://github.com/postmanlabs/postman-app-support/issues/8260

The hover feature is cool, thank’s for that, I didn’t know it. But it does not solve my problem, because again I’d have to manually hover over the variable.

Thanks for your help!

[Kurmavatar (Subramanya Raj)]

That looks great! Our team has already replied on the request.

To keep the discussion continuing on the main thread, will close this out from here

[danny-dainton]

Introducing: Environment Colors for Better Visual Clarity

What’s new:
You can now assign custom colors to environments to make them visually distinct and instantly recognizable.

Who’s it for: All users managing multiple environments - especially teams juggling BETA, STAGE, and PROD setups.

Why it matters:
When working with multiple environments, users often struggle to quickly recognize which one is active. This can lead to mistakes like running requests in the wrong environment (for example, sending test data to production).

1. Color‐coded environments: Each environment can now have a unique color badge, so you can map them to your deployment stages like PROD, STAGE, BETA.
2. Enhanced environment visibility: The currently selected environment now stands out visually across the app, giving stronger emphasis and reducing the risk of context confusion.
3. Improved team awareness: When collaborating, everyone can quickly identify which environment they’re working in - no more “Oops, I thought I was on staging.”