mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5430] [bug]: Secrets in environments are visible and editable for whole team - self hosted #2088
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2088
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SpectoIT on GitHub (Oct 2, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5430
Originally assigned to: @nivedin on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
macOS
Bug Description
We are self hosting Hoppscotch and:
We expected that secrets would be visible only to the user who set them, but any teammate can edit them or see them.
The documentation states:

Is there a setting that has to be changed, or another workflow that we should use? We need to share some variables that are available to everyone, but each person will have their own login and other variables that should not be visible or overridden by others.
Deployment Type
Self-hosted (on-prem deployment)
Version
2025.9.1
@liyasthomas commented on GitHub (Oct 3, 2025):
This behavior is not expected. We are investigating this and will inform you as soon as we have a resolution.
@jamesgeorge007 commented on GitHub (Oct 8, 2025):
Closing this issue since it is now addressed in the latest release. Please let us know if you have any questions.