[GH-ISSUE #3015] [bug]: "My environments" are missing in teams #979

New issue

Closed

opened 2026-03-16 17:55:45 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 17:55:45 +03:00

Owner

Originally created by @HoukasaurusRex on GitHub (Apr 24, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3015

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I navigate to the "Environments" tab, there should be a tab for "My environments" and "Team environments" when in a team workspace - as seen in the picture according to the documentation:

https://docs.hoppscotch.io/documentation/features/environments/

But now I don't see any tab for "My environments".

Is this intentional?

Steps to reproduce

Go to team workspace
Open "Environments"
There will be no tabs for "My environments" or "Team environments"

Environment

Production

Version

Cloud

Originally created by @HoukasaurusRex on GitHub (Apr 24, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3015 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I navigate to the "Environments" tab, there should be a tab for "My environments" and "Team environments" when in a team workspace - as seen in the picture according to the documentation: ![image](https://user-images.githubusercontent.com/23695312/234106278-e6c04137-f5e1-4865-80b3-51338f4b29c0.png) https://docs.hoppscotch.io/documentation/features/environments/ But now I don't see any tab for "My environments". <img width="492" alt="image" src="https://user-images.githubusercontent.com/23695312/234107252-3c4704f7-6546-4015-be6f-76e21de98a11.png"> Is this intentional? ### Steps to reproduce 1. Go to team workspace 2. Open "Environments" 3. There will be no tabs for "My environments" or "Team environments" ### Environment Production ### Version Cloud

kerem

2026-03-16 17:55:45 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 17:56:01 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 25, 2023):

Hi @HoukasaurusRex, we recently made a UI choice which will only allow you to access Team environments while you're in a Team workspace. To access/export your personal environments, switch the to your personal workspace and click on the Environments tab in the sidebar.

The screenshot given the documentation site was an older one. We've updated the docs with the latest screenshot of Environments section.

@liyasthomas commented on GitHub (Apr 25, 2023): Hi @HoukasaurusRex, we recently made a UI choice which will only allow you to access Team environments while you're in a Team workspace. To access/export your personal environments, switch the to your personal workspace and click on the Environments tab in the sidebar. The screenshot given the documentation site was an older one. We've updated the docs with the latest screenshot of Environments section.

kerem commented

2026-03-16 17:56:06 +03:00

Author

Owner

@HoukasaurusRex commented on GitHub (Apr 25, 2023):

Thanks for the reply @liyasthomas . Our team workspace uses personal environment variables for sensitive information like authentication tokens and login passwords that shouldn't be available to the entire team, so I'd like to know what are some ways we can get around this requirement with the updated UI?

Our current workaround is to export our team workspace to our personal workspace periodically and use our personal workspace to test our APIs, but it means we need to keep exporting/importing the workspace regularly to keep our workspace up to date and remember to make changes in the team space, not personal, which is not ideal.

The previous functionality was perfect for our needs, so please let me know if there's a different way we can use this to better suit our needs.

@HoukasaurusRex commented on GitHub (Apr 25, 2023): Thanks for the reply @liyasthomas . Our team workspace uses personal environment variables for sensitive information like authentication tokens and login passwords that shouldn't be available to the entire team, so I'd like to know what are some ways we can get around this requirement with the updated UI? Our current workaround is to export our team workspace to our personal workspace periodically and use our personal workspace to test our APIs, but it means we need to keep exporting/importing the workspace regularly to keep our workspace up to date and remember to make changes in the team space, not personal, which is not ideal. The previous functionality was perfect for our needs, so please let me know if there's a different way we can use this to better suit our needs.