Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.

It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.

I want to be able to Manage multiple Gearset teams from a single Gearset account, and not have to log out and log in again.

Would be good to see the current settings of Source control for Members in read only mode.
Currently what greats us is just a text message:
"Only team owners can change these settings."

If a team member is removed from Gearset team, any template or previous activity can not be removed by anyone else. Leaving some clutter behind. It would be good to have the Owner of the Gearset account/team to have a super admin level access to all templates/data created by other team members so clean up could be managed....

As an admin, I share my deployment filter with developers to add new item to filter. As many team members are working on the release , there is a possibility of jeopardizing the filter's data. I wanted to take a back up of the filter's items periodically. How can i do this?

I have a team of multiple admins that use GearSet and I want to fully control who can deploy where. I can set this up with security today in GearSet by what kind of access I grant. However a user can create their own connection using their credentials and get around the shared connections I have established. I would like the ability to disable a users ability to create new connections which would then only allow them to use pre-existing connections that I have established appropriate security for.

If there is a Gearset user who adds a bunch of orgs, and then quits-- and then a password change is needed for those orgs (or even something simple, such as a nickname change-- it is impossible for another Gearset user to edit the previous Org.

A workaround is possible to remove the previous Org and add a new Org, but this could lead to lost comparison history, something that many businesses (mine included) care a lot about.

Can access to edit Orgs created by other users be added?

My team is working on different projects at the same time, often times independently from each other. The ability to hide all filters personal filters that aren't my own (and maybe selectively share them with a select few team members) would be greatly appreciated!

Where we have a developer-manager, and a team of developers, it would be useful to be able to have a default for sharing org-connections where the manager always has access to their team's orgs.

At the moment, we have to share each org one-by-one.

This has caught us out where a dev team member validated a deployment, then went on holiday thinking that we could deploy it for them. They forgot to share the org-access, so we had to recreate the deployment to get it done.

Have a way to edit other team member's CI jobs, if appropriate permissions are given.

When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.

Hi guys -

In many instances, we would like to restrict user access to certain compare / deploy metadata filters. In our case, it would be rare that all metadata changes are to be deployed and we would like to give our engineers access to only certain filters. This would reduce the risk that items that should not be deployed at a high level will not be deployed. In the current model, if a user has deploy access, they can deploy anything and everything. This is what we are looking to avoid.

Thanks in advance for your time!

Best,

Richard

I'd like to be able to name 'Pairs' of orgs so I don't have to re-select them, like 'DEV to UAT' or 'HOTFIX to Production'

Manage users on "My Team", so we can activate/deactivate users and then save on licences that are not used until reassigned.

When adding a new user having the ability to give the same level of access to all orgs at once would be greatly beneficial.

Likewise, when adding a new org and having the ability to set user access to the new org would save time as well.

We are adding new orgs frequently and will be adding users as well. Saving time on permissions would be great!

Support the ability to group org credentials on the Manage Orgs page by a new Group Name attribute. In managing multiple clients with dozens of PRD and Sandbox orgs it would be extremely helpful to be able to group and filter related credentials by client. However, to expand this feature to support multiple use cases, providing a new Group Name attribute (text) which could contain any value would be fantastic!

Thanks for your consideration,
Mike