Contact sales: +1 (833) 441 7687

Using the team features in Gearset

Gearset's team features are designed to make team collaboration between developers, admins, and release managers ingeniously simple:

  • Add colleagues to your team with a few clicks
  • Share and delegate access to your Salesforce orgs
  • View deployment history and user activity across your team
  • Collaborate on the creation and validation of deployment packages
  • Create and share automated CI, change monitoring and unit testing jobs within teams
  • Set user roles and permissions

You can read the walkthrough below, or watch our team features demo demo to see it in action.

Step 1: Creating your own team in Gearset

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 for the person you'd like to add to your team.

Note: Only team owners can invite users and manage team settings.

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

Step 2: Setting team member Salesforce org access permissions

With users added to your team, it's time to share some Salesforce org connections. Sharing org connections allows other members of your team to view or deploy changes to an org without having access to your login details (username/password). You can control what level of access they have to the org, and change or revoke access at any point.

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 permission 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.

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.

Once you have shared an org with a team member, it will appear in their list of authorized orgs on the Compare & Deploy screen, and the Manage orgs tab. If they have the required permissions, they will be able to run comparisons, build validated deployment packages, or deploy changes as if they had authorized the account themselves.

Note: if a user deploys changes to an org using a delegated account, the deployment will appear in Salesforce as if it was run by the original user who shared their credentials.

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 or a pdf report of what was deployed, and export the results of the deployment as a csv file.

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. To create a draft, simply click the Save draft deployment button on the comparison results. Give the draft a name, and it will save the snapshots of your orgs and any selected metadata items. If you want to update your draft after changing your metadata selection, simply click the save button again to update your draft.

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.

Note: draft deployments involving a source control repository cannot be shared with your team.

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 continuous integration (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 what has changed.