Collaboration, delegated Salesforce org access and compliance in Gearset

Stephen Chambers on September 28th 2016


Implementing a reliable and efficient Salesforce release management process is difficult. The main blockers to achieving this goal include factors such as Salesforce environment complexity, coordinating with remote teams in different time zones, ensuring legal compliance and having a clear audit trail of changes.

The solution to removing those blockers has now arrived with the release of our team features in Gearset. Solve collaboration headaches, control access to orgs, and keep an audit trail of what's happening throughout your Salesforce landscape. You can read the walkthrough below, or watch our team features demo to see it in action.

Step 1: Creating your very own deployment A-team

You will need to first of all make sure that you've not previously been invited to a team, and are the team owner when you've first created your Gearset account.

1. To begin adding team members, visit the manage account page via the menu in the top right, then enter the email address of the Salesforce or Google account of the person you'd like to add to your team.

Adding new member email address
Note: Only team owners can invite users and manage team settings.

2. After accepting your invitation, your team member will appear in the team summary section underneath.

New team member added


Step 2: Setting team member Salesforce org access permissions

With users added to your team, it's time to share some Salesforce org connections.

Navigate to the user access page via the Configure team org access permissions link below the table, or from the account menu. From the assignment options, choose the Salesforce org(s) that you want to share and one of the four permission levels available.
The four levels of permissions are:

  1. None: the connection to this Salesforce org will not be shared with this team member. This is the default when a new team member or org is added.
  2. Compare: the team member can use this org for comparisons only. They cannot deploy changes.
  3. Validation: the team member can use this org for comparisons and create validated deployment packages. They cannot deploy changes.
  4. Deployment: a team member has full comparison and deployment access to this org.

Available team access permissions

Below you can see that two of my team members have access to my [email protected] org, one of whom has validation access and the other has full deployment access.

Team member access permissions


To see a complete overview of the orgs you have access to, either as the owner or having been given shared access by a team member, visit the main manage orgs page in Gearset.


Step 3: Get collaborating! Draft deployments, shared history and automated jobs

Shared team deployment history
The deployment history of your team is shared across all team members and can be accessed via Deployments > deployment history. From there you can see all previous deployments made through Gearset, download the deployment package, a pdf report of what was deployed and export the results of the deployment as a csv file.

Shared team deployment history


Creating, sharing and deploying draft deployments
When preparing for a deployment, you can save your current selection as a draft and iteratively include the objects to be deployed over time. Provided the validation or deployment permissions have been set for a team member, they can visit the draft deployments page to see all currently active draft deployments and edit the draft to help review, edit and even deploy the changes when ready.

Shared team draft deployments


Accessing automated change monitoring, CI and unit testing jobs
Gearset's enterprise tier provides automation features, such as creating jobs to monitor for org metadata changes, unit testing automation and CI. If you've provided access to an org, team members can view each of the jobs, receive automated notifications of the outcomes and review the results. So, if Gearset has detected changes in the metadata of a Salesforce org for example, team members can be alerted and access the details to understand exactly how their Salesforce org has changed.

Shared monitoring jobs


Conclusion

Gearset's overall aim is to simplify the Salesforce release management process for everyone. Providing a way for teams to collaborate, share information, track changes and delegate access to any Salesforce org will remove some of the biggest blockers teams face when trying to streamline their release management.

If you're looking for a way to bring calm to your deployment chaos, then you and your team can try out the latest features with our 30 day free trial of Gearset and see for yourself how much easier deployments can be.


Ready to get started with Gearset?

Sign up now to start your completely free 30 day trial
try it now