People tab
The same person has an account in the VCS (GitLab or GitHub), in the tracker (Jira or the built-in tracker) and in Merge Pilot. When Merge Pilot assigns a change approval, names the author of a change in the tracker, or creates a change approval in someone's name, it has to find that person's tracker account. The People tab says how, and checks that it works for everyone in the company.
Company page → People. Company admins of the company and platform admins change these settings; they are saved with Save changes (see Saving) and are not held for four-eyes review.
How a person is recognised
- Merge Pilot account ↔ VCS account. A person links their GitLab or GitHub account in My profile (or signs in with it). Merge Pilot then knows which Merge Pilot account a VCS user name belongs to, per VCS connection; the user name is compared without regard to case. Only active accounts of the company count. A Merge Pilot user name is never taken for a VCS user name: they are separate.
- Merge Pilot account → tracker account. Found as described below: the person's own tracker account first, then the company's rule.
People who have not linked their VCS account cannot be assigned a change approval and cannot vote. When two Merge Pilot accounts have linked the same VCS account, nobody can tell which person it is, so it counts as no one.
The built-in tracker
In the built-in tracker the tracker account is the Merge Pilot account. A person is found there once they have linked their VCS account; the rule on this tab and tracker accounts set per person are not used.
The same person in the tracker
How Merge Pilot finds a GitLab or GitHub user in the tracker: the developer a change approval is assigned to, the merge request's author, and the change approval's creator. A person's own tracker account, set on the Users page, always comes first.
| Setting (label in the UI) | What it does | Default | Allowed values | Who can change it | API field |
|---|---|---|---|---|---|
| Finding people in the tracker | The rule used for anyone without a tracker account of their own | The same user name | See the options below | Company admin, platform admin | people.tracker_match |
The options:
- The same user name (
username): GitLab and the tracker sign people in from the same directory (LDAP, Active Directory): jdoe in GitLab is jdoe in Jira. The person's VCS user name is looked up in the tracker. - The email address (
email): The email of the Merge Pilot account. Needed for Jira Cloud, which has no user names, or when user names differ between the systems. Only people with a Merge Pilot account linked to the VCS account are found. - Only accounts set per person (
mapping): An administrator sets each person's tracker account on the Users page. People without one are never assigned a change approval. A decision in the tracker counts only for the person whose tracker account is set; an email that happens to match is not used.
When the company has an active Jira Cloud connection and the rule is The same user name, the tab warns: Jira Cloud has no user names. Choose "The email address", or set people's tracker accounts on the Users page.
Tracker accounts set per person
A person's Tracker account (their user name, email or account ID in the tracker) is set on the Users page by a company admin or platform admin (see Roles and users). It always comes before the company's rule. Set it for the people the rule does not find.
With The email address, when Merge Pilot assigns a change approval in Jira (when it is created, when someone takes it or takes it over, or when it is assigned again) and the email leads to exactly one Jira account, it stores that account as the person's tracker account, so that their decisions, which Jira reports by account, are counted as theirs. This happens only for people without a tracker account, and not when another person of the company already has that account. Each time, the audit log records tracker_account_learned.
Who creates the change approval
| Setting (label in the UI) | What it does | Default | Allowed values | Who can change it | API field |
|---|---|---|---|---|---|
| Who creates the change approval | Whose name the change approval is created in, in the tracker | The tracker connection's account | See the options below | Company admin, platform admin | people.change_approval_reporter |
The options:
- The tracker connection's account (
service_account): Every change approval is created by the account Merge Pilot uses in the tracker. - The author of the merge request (
author): The change approval is created in the author's name, found like the assignee. In Jira the connection's account needs the Modify Reporter permission; when the author has no tracker account, the connection's account creates it.
Check people
Looks every active person of this company up in the tracker with the saved rule, so you see who cannot be assigned a change approval or recorded as its creator. Save changes first.
- Without a tracker connection the card says Add a tracker connection first.
- With more than one active tracker connection, choose one (Tracker connection); the company's default tracker connection is chosen first.
- Check people runs the check. It reads the tracker, and changes nothing.
The result line says All 12 found in the tracker., 3 of 12 not found., or This company has no active people yet. The table has a row per person:
| Column | Shows |
|---|---|
| Person | The display name and the Merge Pilot user name |
| GitLab / GitHub | The linked VCS user name, or Not linked (Not assigned change approvals and cannot vote until they link GitLab/GitHub in My profile) |
| Looked up as | What was searched in the tracker: the tracker account set for the person (marked (set per person)), else what the rule gives; nothing to look up when the rule gives nothing (for example Only accounts set per person and no account set, or the built-in tracker and no linked VCS account) |
| In the tracker | The account the tracker found, or Not found, No tracker account set, or Error: … when the tracker answered with an error |
When someone is not found: Fix it by choosing another rule above, or by setting the person's tracker account on the Users page.
Limits: the check covers the first 300 active people of the company, by user name. Each lookup waits up to 15 seconds for the tracker.
Who: company admins of the company and platform admins.
API: GET /api/v1/connections/{trackerConnectionId}/people-check answers a list with, per person, user_id, username, display_name, vcs_username, linked, tracker_name (what was looked up), mapped (a tracker account set per person), found (the account found, empty when none) and error. It answers 400 for a VCS connection and 502 when the tracker could not be asked.
Access people got through Merge Pilot
Repository and group access people gave themselves by joining through Merge Pilot, which Merge Pilot no longer tracks.
Merge Pilot records the access people get by joining through it: a repository on GitLab or GitHub, and a group on GitLab (see Membership). It stops tracking that access, cleaning only its own records, when:
| Released (label in the UI) | When | API value |
|---|---|---|
| Deactivated | The person was deactivated or deleted | deactivated |
| Moved to another company | The person was moved to another company | moved_to_another_company |
| Made platform admin | The person was made platform admin | made_platform_admin |
| VCS account unlinked | The person unlinked their GitLab or GitHub account in My profile: Merge Pilot can no longer tell which account the access was given to. Their tokens stay tracked | unlinked |
| Repository removed from Merge Pilot | Change management was removed from the repository, or it is no longer watched (the access to that repository and the tokens created on it) | project_removed |
| Connection deleted | The connection the access was given through was deleted | connection_deleted |
| Company deactivated | The company was deactivated | company_deactivated |
Merge Pilot never removes access on GitHub or GitLab when this happens, so that access may still exist there. Someone who joins the same repository or group again later is tracked again, and the released record stays until it is dismissed. When a release fails (the database could not be written), Merge Pilot tries again within the hour, and the audit entry says so (sweep: true).
The card lists the released access, newest first:
| Column | Shows |
|---|---|
| Repository | The repository's path, or the group's path marked Group, and the connection's name |
| Person | The GitHub or GitLab user name, and the Merge Pilot user |
| Role | The role they joined with (for example Write); Sent as an invitation when GitHub sent an invitation to accept |
| Granted | When they joined |
| Released | When Merge Pilot stopped tracking it, and why (the table above) |
Check the access on GitHub or GitLab and remove it there if it should go. Then Dismiss deletes the record after Dismiss this record? (the access on the VCS is not changed). Nothing to check: no released access. when the list is empty.
The audit log has vcs_access_grants_released (with the reason, the count and the list: repository or group, connection, VCS user name and role) when access is released, and vcs_access_grant_dismissed when a record is dismissed. Each release is also announced as the VCS access to review notification (access_released), to the routes that take it and by email to the company admins (see Events).
Who: company admins of the company and platform admins.
API: GET /api/v1/companies/{id}/vcs-access-grants?released=true lists it (each with kind: project, with repo_id and repo_path, or group, with group_id and group_path); DELETE /api/v1/companies/{id}/vcs-access-grants/{grantId} dismisses one (409 for access Merge Pilot still tracks: the person leaves it on the project page). Without released=true, the list is the access Merge Pilot tracks.
Tokens created through Merge Pilot
Project access tokens and deploy tokens Merge Pilot created for people who left the company, on a repository removed from Merge Pilot, through a deleted connection, or in a deactivated company.
When someone leaves the company (deactivated, moved to another company or made platform admin), the GitLab tokens Merge Pilot created for them (see Tokens) keep working: Merge Pilot never revokes them on its own. Removing the repository from Merge Pilot, deleting the connection and deactivating the company do the same for the tokens created there (the reasons are those of the access above; unlinking a VCS account releases no token). Tokens that were revoked or have expired are not listed.
The list below the released access shows each token with its kind, role and scopes, the repository and connection, who asked for it, its expiry, and when and why it was released.
- Revoke revokes the token on GitLab with Merge Pilot's account after Revoke this token?; the record stays, marked revoked, until dismissed. A token of a deleted connection cannot be revoked here (Connection deleted: revoke it on the VCS).
- Dismiss deletes the record after Dismiss this token's record? (the token on GitLab is not changed).
Nothing to check: no released tokens. when the list is empty.
The audit log has vcs_issued_tokens_released when tokens are released, vcs_revoke_token when one is revoked here, and vcs_issued_token_dismissed when a record is dismissed. None of them holds a token's value.
API: GET /api/v1/companies/{id}/vcs-issued-tokens lists them; POST /api/v1/companies/{id}/vcs-issued-tokens/{tokenId}/revoke revokes one (409 when its connection was deleted or it is revoked already); DELETE /api/v1/companies/{id}/vcs-issued-tokens/{tokenId} dismisses one (409 for a token Merge Pilot still tracks: revoke it on the project's Tokens tab).
API
PUT /api/v1/companies/{id} with people: {"tracker_match": "username" | "email" | "mapping", "change_approval_reporter": "service_account" | "author"}. An empty or missing value means the default. See Company API.
Related pages
- Approval: assignment of change approvals and how decisions in the tracker are counted.
- Roles and users: the Users page, where tracker accounts are set, and My profile, where people link their VCS accounts.
- Jira and Built-in tracker: the tracker connections.
- Approvals: the company's approval settings, including stand-ins.
Video tutorial
Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →