[GH-ISSUE #4722] [feature]: Syncing of global environment variables (still overwritable in Secrets tab) #1762

New issue

Open

opened 2026-03-16 21:38:54 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 21:38:54 +03:00

Owner

Originally created by @iDschepe on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4722

Is there an existing issue for this?

I have searched the existing issues

Summary

Description:
For teams working collaboratively, it would be highly beneficial to have global environment variables that are synchronized across all team members. Each individual should still have the ability to override these variables via the Secrets tab.

Expected Behavior:

Global environment variables should be synced across all team members.
Individual users should be able to override these global variables in their personal Secrets tab.
If a user does not override a variable, the global value should be used.

Would this feature be feasible to implement?

Why should this be worked on?

Why is this useful?
Teams often work with shared API endpoints, authentication tokens, or configurations that should be consistent for everyone globally and not specifically bound to an environment.

Originally created by @iDschepe on GitHub (Feb 4, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4722 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary **Description:** For teams working collaboratively, it would be highly beneficial to have global environment variables that are synchronized across all team members. Each individual should still have the ability to override these variables via the Secrets tab. **Expected Behavior:** - Global environment variables should be synced across all team members. - Individual users should be able to override these global variables in their personal Secrets tab. - If a user does not override a variable, the global value should be used. Would this feature be feasible to implement? ### Why should this be worked on? **Why is this useful?** Teams often work with shared API endpoints, authentication tokens, or configurations that should be consistent for everyone globally and not specifically bound to an environment.

kerem added the

feature

label

2026-03-16 21:38:54 +03:00

kerem commented

2026-03-16 21:39:05 +03:00

Author

Owner

@Manasvisharma09 commented on GitHub (Jul 23, 2025):

Hi! This is a really useful feature. I'd love to explore and contribute to implementing this if it’s still open 🙂

@Manasvisharma09 commented on GitHub (Jul 23, 2025): Hi! This is a really useful feature. I'd love to explore and contribute to implementing this if it’s still open 🙂

kerem commented

2026-03-16 21:39:10 +03:00

Author

Owner

@alexey-krylov commented on GitHub (Mar 6, 2026):

+1
In my case global environments are not working at all - no one else can see variables i am adding. We end up creating per-workspace Global environment

@alexey-krylov commented on GitHub (Mar 6, 2026): +1 In my case global environments are not working at all - no one else can see variables i am adding. We end up creating per-workspace Global environment

kerem referenced this issue

2026-03-17 01:05:21 +03:00

[PR #1762] [MERGED] fix: pkce params match rfc naming convention #3476