[New Change] Simplifying workspace types & permissions

Hi everyone,

My name is Taylor Pechacek, Head of Product for API Collaboration Core at Postman. I just wanted to share a change to workspaces in Postman that aims to simplify how different internal workspace types are used and the permissions of managing user access within those different workspace types.

No action is needed on your part and these changes do not currently affect Enterprise users, but will be coming in the future as we work with you all to roll this out seamlessly.

What’s changing?

We are simplifying how people create, manage, and search different workspaces which will reduce confusion and make it easier to use workspaces. Moving forward:

  1. Personal’, ‘Team’ and ‘Private’ workspaces will now be called Internal Workspaces.
  2. This is a UI/UX change. Your data and permissions on existing workspaces remain unchanged.
  3. Within Internal Workspaces you can control user access management and permissions without having to change workspace types. You simply set the workspace access to ‘anyone in my team’ or ‘only you and invited people’ and share with specific people.

So there are now three workspaces to choose from:

At the time of create, you can select the permission level to lock it down to only yourself and open it up to others later, or invite specific people. The permissions can still be referred and thought of as being ‘personal’ meaning it’s only accessible to you, ‘private’ meaning it’s accessible to you and specified number of people, and ‘team’ meaning it’s accessible to everyone in your team.

Once a workspace is created, you can use the blue ‘Invite’ button in the top header or go into workspace settings to change the workspace access - no need to migrate or move collections around to different workspace types!

What about existing workspaces?

Your current personal, team, or private workspaces will simply be renamed as Internal Workspaces in Postman. Everything else stays the same in the backend. All your data and settings remain unchanged and you can update permissions anytime via settings.

If you go to workspace search, you will see the type and access columns to easily see what access a workspace has. You will also notice the locked icon for workspaces with restricted access.

Do I need to do anything?

No—your data and permissions remain exactly the same. This update is purely a renaming and UI change designed to simplify your experience. We will continue to simplify and streamline access management so that API collaboration can happen where and when you want it to.

Impact on new customers

New users who signup will start with an internal workspace, accessible by anyone in their team, making it much simpler to invite a friend or colleague when you’re ready but doesn’t get in your way if you want to work individually.

Why are we making this change?

  • Simplification: Three self-explanatory options based on the type of work you are doing make it easier to choose the right workspace for your needs. Within the workspace, you can easily manage different access & permission settings so the right people are collaborating on the right things. The current model conflates type and access so we are making this more explicit and hopefully easier to manage!
  • Reduced Friction: APIs are inherently collaborative. When you do need to share an API with someone, it’s simply a matter of inviting users and managing their access to the workspace.

When will this happen?

This has been rolling out for a couple of weeks, so you may have already seen this change. Everyone, except for enterprise users, should have this by March 21st.

Our rollout plan for customers on our Enterprise plan is on a different timeline. Leave a comment if you want to know more.

Any questions or feedback, please let us know in the comments below. Thanks, as ever, for being a Postman user :postman:!

11 Likes

I love it! As a power use I often got a lot of questions regarding workspace/collection permissions from my user base. This is a great step to simplify things yet retain granular control.

4 Likes

Nice @pozil thank you for sharing this! That’s the idea. The only concern I have is making sure the visibility of these permissions is still clear, it’s easy to understand, and easy to navigate.

Having personal, private, team up front as types did make visibility somewhat easier - if i create a workspace type personal I know it’s just for me. Creating an internal workspace - how can I be sure/easy to grok what access settings I have for that at time of creation and management ongoing.

But because the old model kind of conflates a few things and in some cases you had to switch between those previous ‘types’, moving collections/requests around, there was more friction there. This is meant to be a nice quality of life improvement and we want to continue to simply as Postman grows (in terms of overall product functionality).

So that’s what we are watching and listening for and will respond to any feedback, so please share if you have any other aspects we can improve to build on this change. It’s a relatively straight forward UX change, but it allows us to build future improvements in permissions (which we will continue to invest in) to make that simple, flexible, and powerful!

3 Likes