Team owner Team mate
Requested Azure DevOps permissions

When you install GitLive on a Azure DevOps organization or personal account we request permission to the following scopes

Identity (read): Grants the ability to read identities and groups.

We use this to identify who you are and which organizations you own or belong to.

Graph (read): Grants the ability to read user, group, scope, and group membership information.

We use this to ensure only teammates that have access to a repository on Azure Devops are able to view another teammate's working copy of that repository. See Access Control in the section below for more on how this works.

Code (read): Grants the ability to read source code and metadata about commits, changesets, branches, and other version control artifacts. Also grants the ability to search code and get notified about version control events via service hooks.

To enable the realtime sharing of a teammate's working copy changes, GitLive needs to access the code.

We maintain patch files for each teammate's changes in our database; these files only contain the differences between the teammate's working copy version of a file and the latest repository version, we do not store complete copies of your source files.

Once a teammate pushes their changes the patch file is permanently deleted from our database.

MemberEntitlement Management (read): Grants the ability to read users, their licenses as well as projects and extensions they can access.

We use this to ensure only teammates that have access to a repository on Azure Devops are able to view another teammate's working copy of that repository. See Access Control in the section below for more on how this works.

Project and team (read): Grants the ability to read projects and teams.

We require this permission to show your projects and team within GitLive.

Work items (read): Grants the ability to read work items, queries, boards, area and iterations paths, and other work item tracking related metadata. Also grants the ability to execute queries, search work items and to receive notifications about work item events via service hooks.

We access these resources to show what issue each of your teammates are working on and to allow them to get notified, view and respond to discussions directly from GitLive.

Access control

To ensure all users can only access the relevant data, we maintain strict access control. Users can only see a fellow teammate’s data for the repositories they share access to. In addition, users with only read access to a repository are not visible to their fellow teammates.

Access is synchronized with your Azure Devops member privileges; removing a member's access to a repository or organization on Azure DevOps removes their access on GitLive.

Deleting your data

To completely remove all data we hold about your team, including repository and working copy data, simply revoke GitLive's access under "Manage Authorizations" within your Azure DevOps organization or personal account.

Individual users' data may persist if they also belong to other organizations, otherwise they can delete this data by revoking GitLive's authorization on their personal Azure DevOps accounts.

To learn more about how we collect and process your data, you can also read our Privacy Policy