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

How teams work in Gearset

Teams are the basis of collaboration in Gearset. Users within a team can see each others' activity, such as deployments and automation jobs, to enable seamless knowledge sharing. Users can also share access to Salesforce orgs they have authorized within a team, and set access permissions for their team mates. Team owners can manage license assignment and team admin, such as inviting new team members and setting overall team permissions (learn more about team owners here).

Shared team activity

Most deployment-related actions in Gearset are automatically visible to other members of your team, including:

All team members will be able to view the high level information about each of these actions. Depending on your team setup and any delegated org credentials, they may also be able to take actions from some of these items, such as deploying a validated package.

Shared automation 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).

Automation jobs are also shared within teams. Any team member can view the current status and history for the following jobs created by their team mates:

Custom notification settings can also be set for these jobs to notify multiple members of your team when they run. For example, if a change monitoring job detects changes to your production org, multiple team members can be alerted and access the details to understand exactly what has changed.

Did this answer your question?