The option to “Share” a Collection or Environment Definition used to be present so that the object could be accessed from different collections. (I Noticed this change in version 9.1.1) With the latest version of Postman All I see when I Select the “Share” option is “Share link to the collection/en…

As a Product Manager you should have opted to give your customers a choice to keep the existing share or move to the Fork/PR method. Taking one lot of customer feedback and impacting the rest of your client base is not a wise choice. You say you made the change due to customer feedback, well we ar…

I agree 100%. Removing a feature rather than providing an alternative and giving people the choice is extremely disruptive and a hasty decision without thought to the impact it would have on people who were using the previous solution well. I really hope Ramji considers re-instating this as an opti…

Guys it’s very frustrating, we used a lot this feature and now there is not a good and simple alternative. Bad way to manage a breaking change

Hey everyone! I understand how frustrating it is when things stop working and workflows have to change. It’s our effort to make things easier for everyone that we made this decision. We’ve recieved a lot of feedback from users where it’s often times confusing and a challenge to keep collections in …

@kevinc-postman What it seems that you are missing is that a lot of folks liked the “share” feature and for their own reasons do not want, need or desire to use the “fork/pull requests”. For the usage model and manner in which Postman has been implemented in my organization, forking and pull reque…

I understand the idea behind the feature because it was always weird for me to work using a collection shared from my team workspace to my personal workspace and any change I did “locally” would alter the collection for everybody. A forking model seems decent enough, especially if there are some sor…

Taking this away is just really bad. I get the forking feature, it’s fine if you want this behavior. But that doesn’t mean that many of your customers use and appreciate the sharing feature. I like to have my custom workspace that contains just the collections I want, but that doesn’t mean that I w…

Please bring back the sharing functionality. This is a major step backward and a hindrance to workflow. The fork/pull request option is significantly more work to accomplish something that the sharing feature made so easy for so many people.

We want to split workspaces based on teams working on different slices of product but they share environments. Without the ability to share the environment, maintainability goes for a toss.

We recently introduced the capability to fork environments. You can use it to reuse an environment across multiple workspaces: Introducing Environment Forking and Pull Requests | Postman Blog

What Happened to Sharing a collection/environment across Workspaces

Help Hub

joint-operations-ar3 (Deepak Aggarwal) June 15, 2022, 9:03am 33

Environment Forking is a good solution if this issue is resolved

Topic		Replies	Views
Workspaces - Shared Requests Help Hub workspaces	16	7210	January 6, 2025
Postman Pro team workspaces are dangerous Help Hub	5	3906	May 10, 2019
[Postman API] Fetching owned and "shared" environment with the API Help Hub	0	716	May 11, 2018
Collection management Help Hub	4	806	June 19, 2019
Forking private collections between team workspaces Help Hub collections , fork-and-merge	0	660	August 16, 2022

What Happened to Sharing a collection/environment across Workspaces

Related topics