[GH-ISSUE #2924] [feature]: Ability to specify if saving to local or team environment #944

Closed
opened 2026-03-16 17:47:04 +03:00 by kerem · 3 comments
Owner

Originally created by @itsJoKr on GitHub (Feb 15, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2924

Is there an existing issue for this?

  • I have searched the existing issues

Summary

When working with the team we use team environment with variables like:

  • BASE_API
  • REDIRECT_URI

But often we will need to login to perform some requests. For these we need to save locally since every team members will have different values:

  • access_token
  • refresh_token

The problem is that if we select Team environment all the variables will be saved to that team environment and that can mess up with other team members while they are working at the same time.

Our current workaround is that everyone needs to setup and import the local environment.

Two ways we can solve this:

  1. In postman, this is solved in a way that we have initial value which is shared across the team, and then every pm.environment.set will update the variable only locally. Refer to image below:

image

  1. Let the developer specify to which environment to save. For this, we could maybe use Global environment (although Global might not be best use-case for this since it's a more per-environment setting):
pw.env.set("variable", "value");
pw.env.global.set("variable", "value");

Why should this be worked on?

It prevents multiple team members from working together and using team environments simultaneously.

Originally created by @itsJoKr on GitHub (Feb 15, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2924 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary When working with the team we use team environment with variables like: - BASE_API - REDIRECT_URI But often we will need to login to perform some requests. For these we need to save **locally** since every team members will have different values: - access_token - refresh_token The problem is that if we select **Team environment** all the variables will be saved to that team environment and that can mess up with other team members while they are working at the same time. Our current workaround is that everyone needs to setup and import the local environment. ### Two ways we can solve this: 1. In postman, this is solved in a way that we have **initial value** which is shared across the team, and then every `pm.environment.set` will update the variable only locally. Refer to image below: ![image](https://user-images.githubusercontent.com/11093480/218996391-7be85cd6-69f1-4d3d-abf5-7d1fea37e456.png) 2. Let the developer specify to which environment to save. For this, we could maybe use Global environment (although Global might not be best use-case for this since it's a more per-environment setting): ``` pw.env.set("variable", "value"); pw.env.global.set("variable", "value"); ``` ### Why should this be worked on? It prevents multiple team members from working together and using team environments simultaneously.
kerem 2026-03-16 17:47:04 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@syamsoul commented on GitHub (Aug 11, 2023):

hope this feature will be implemented soon...

<!-- gh-comment-id:1674181991 --> @syamsoul commented on GitHub (Aug 11, 2023): hope this feature will be implemented soon...
Author
Owner

@iDschepe commented on GitHub (Feb 4, 2025):

Would be very helpful.

<!-- gh-comment-id:2633599957 --> @iDschepe commented on GitHub (Feb 4, 2025): Would be very helpful.
Author
Owner

@liyasthomas commented on GitHub (Aug 4, 2025):

This feature is now available in Hoppscotch.
Docs: https://docs.hoppscotch.io/documentation/features/environments#types-of-values-in-an-environment

<!-- gh-comment-id:3149163130 --> @liyasthomas commented on GitHub (Aug 4, 2025): This feature is now available in Hoppscotch. Docs: https://docs.hoppscotch.io/documentation/features/environments#types-of-values-in-an-environment
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#944
No description provided.