Collection Editor Role by Default

LiamC · March 4, 2020, 10:41am

Hi,

Is there a way of making it so when I create a Collection, it assigns all members of my team to the ‘Editor’ role by default so I don’t have to manually change the Role permissions for each collection?

Kurmavatar · March 7, 2020, 8:33am

Hi @LiamC

Yes, so once you create the collection and click on “Manage collection” - you should find an option to choose roles for “Everyone in the team” as below:

Screenshot 2020-03-07 at 2.02.08 PM

Hope this helps!

LiamC · March 9, 2020, 9:09am

Yeah I’m already doing that.

Wanted to know if this can be a default occurrence when a collection has been made.

LiamC · March 12, 2020, 9:54am

Alright guess not then.

Kurmavatar · December 21, 2020, 6:12am

For everyone who is looking for a way to do this - we currently do not have this flow in place but our team is tracking this as a feature request in the below GitHub link. Feel free to add any comments/ up-vote that should help the team build this further

github.com/postmanlabs/postman-app-support

Permissions for a new team collection - Need to have a global setting or ability to set during creation

opened 11:03PM - 03 Jan 19 UTC

closed 10:15AM - 06 Jul 22 UTC

thetreythomas

feature Roles and Permissions product/collaboration

**Environment** Windows 10 Postman v6.6.1 **Is your feature request related… to a problem? Please describe.** By default, when you create a new collection on a team, the permissions are set by default to "Can view". As a team, we are constantly adding collections based on a feature we might be testing individually, but will be used by the entire team later. It's cumbersome to have to go in and modify each collection to "Can Edit" every time you create a new collection. **Describe the solution you'd like** Maybe two options: 1. When creating a new collection for a team, there is another tab at the top to allow the choice to be made. 2. A more global setting for the team workspace, that would allow the default behavior of certain things, with the collection permission to be one of them. This would be specific to the workspace, so if you created another workspace, you would have the ability to have different default settings. A working scenario would be one workspace would be for internal dev and QA testing, and the other would be a customer facing where you only want them to view, and not edit. **Describe alternatives you've considered** There doesn't appear to be an alternative. Thanks!