starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #5207] [feature]: Ability to share workspaces #1988

New issue

Closed

opened 2026-03-16 22:46:17 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 22:46:17 +03:00

Owner

Originally created by @elieobeid7 on GitHub (Jun 27, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5207

Is there an existing issue for this?

I have searched the existing issues

Summary

My company is looking to adapt Hoppscotch; it would be great to have the ability to share a workspace with a link, rather than inviting all the users individually, like Postman.

If you want to grow your software, you have to target companies and not just individual users. Companies are used to using Postman, so it would be great to see what useful features Postman has and implement them, which would ease the transition to Hoppscotch

Why should this be worked on?

Because companies need it, companies have thousands of users. You can't add them individually; you generate a link and share it on Slack or by email to all, and they join.

Since hoppscotch doesn't support teams and we have to have one, we create a workspace and invite everyone. Most companies will do that.

Originally created by @elieobeid7 on GitHub (Jun 27, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5207 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary My company is looking to adapt Hoppscotch; it would be great to have the ability to share a workspace with a link, rather than inviting all the users individually, like Postman. If you want to grow your software, you have to target companies and not just individual users. Companies are used to using Postman, so it would be great to see what useful features Postman has and implement them, which would ease the transition to Hoppscotch ### Why should this be worked on? Because companies need it, companies have thousands of users. You can't add them individually; you generate a link and share it on Slack or by email to all, and they join. Since hoppscotch doesn't support teams and we have to have one, we create a workspace and invite everyone. Most companies will do that.

kerem

2026-03-16 22:46:17 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 22:46:33 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jun 27, 2025):

Workspaces in Hoppscotch are private by default. Ability to make public workspace are in our roadmap.

Possibly a duplicate of #680 hence closing.

@liyasthomas commented on GitHub (Jun 27, 2025): Workspaces in Hoppscotch are private by default. Ability to make public workspace are in our roadmap. Possibly a duplicate of #680 hence closing.

kerem commented

2026-03-16 22:46:38 +03:00

Author

Owner

@elieobeid7 commented on GitHub (Jun 27, 2025):

@liyasthomas no I'm not suggesting public workplaces, sharing my company workplace publicly is stupid

I want to share a link with my team
When they request to join, I receive an email asking me to accept them as team members

What kind of stupid person would want to share their company data publicly? It stays private, just rather than entering emails individually, you share a URL and then accept people

Haven't you ever used Postman? Besides what's wrong with you and with this shitty mentality

Close questions first, then ask questions later

Why are you in a hurry to close tasks? Ask your questions, wait for the other person to answer, and then close.

This is a very bad approach to life in general. I fire developers who jump to conclusions, because they create many bugs, they don't understand the requirements, they never ask their coworkers for help, they're not team players, that's how bugs are created. Jumping to conclusions without prior discussion.

You are in charge of hopscotch; you shouldn't encourage this behavior.

I mean, even you know

Possibly a duplicate, possibly

Even though you're not sure, you still decided to close it

@elieobeid7 commented on GitHub (Jun 27, 2025): @liyasthomas no I'm not suggesting public workplaces, sharing my company workplace publicly is stupid - I want to share a link with my team - When they request to join, I receive an email asking me to accept them as team members What kind of stupid person would want to share their company data publicly? It stays private, just rather than entering emails individually, you share a URL and then accept people Haven't you ever used Postman? Besides what's wrong with you and with this shitty mentality > Close questions first, then ask questions later Why are you in a hurry to close tasks? Ask your questions, wait for the other person to answer, and then close. This is a very bad approach to life in general. I fire developers who jump to conclusions, because they create many bugs, they don't understand the requirements, they never ask their coworkers for help, they're not team players, that's how bugs are created. Jumping to conclusions without prior discussion. You are in charge of hopscotch; you shouldn't encourage this behavior. I mean, even you know **Possibly a duplicate, possibly** Even though you're not sure, you still decided to close it

kerem commented

2026-03-16 22:46:43 +03:00

Author

Owner

@elieobeid7 commented on GitHub (Jun 27, 2025):

@liyasthomas

this is not the first time you do this, you did this here as well and that's just me, who knows how often do you do this

https://github.com/hoppscotch/hoppscotch/issues/5161

You closed a bug report without even testing it or understanding the issue. This is very bad.

Why are you the one active on GitHub issues anyway? I understand you're a CEO and have a million things going on. Delegate this task to someone with more time on his hands, and you take care of more urgent stuff. There's gotta be someone in your team with enough time to test and discuss bug reports. If you don't have a QA hire one.

Or even, leave issues open until you have enough time to read them, just don't jump on them real fast and close them. I have 8 issues open with VSCode repo, they're assigned to people and waiting to be addressed and that's fine. It's better to leave issues open for a very long time than to prematurely close them.

@elieobeid7 commented on GitHub (Jun 27, 2025): @liyasthomas this is not the first time you do this, you did this here as well and that's just me, who knows how often do you do this https://github.com/hoppscotch/hoppscotch/issues/5161 You closed a bug report without even testing it or understanding the issue. This is very bad. Why are you the one active on GitHub issues anyway? I understand you're a CEO and have a million things going on. Delegate this task to someone with more time on his hands, and you take care of more urgent stuff. There's gotta be someone in your team with enough time to test and discuss bug reports. If you don't have a QA hire one. Or even, leave issues open until you have enough time to read them, just don't jump on them real fast and close them. I have 8 issues open with VSCode repo, they're assigned to people and waiting to be addressed and that's fine. It's better to leave issues open for a very long time than to prematurely close them.