Invite new users to join your team

Administrators can invite anyone to become a member of your team using their email address, or using an invitation link.

📘
For Enterprise Server, If you have Automatic Sync with GitHub enabled and SCIM disabled, users are automatically added as members on DeepSource teams for their corresponding GitHub organizations.

📘
If your team has a paid per-user subscription, an empty seat must be available before you can invite a new member to join the team. For more information, see our Pricing plans.

Go to the Dashboard. On the top left corner, click on the account switcher and then select the team you want to add the user to.
Go to the Home tab on the left sidebar.
Go to the Members tab from the list of tabs on the team header.
Click on the Invite new member button.
You can now invite the team members via e-mail or via invitation link.

Via email

Enter the email address of the person you want to invite.
Choose the appropriate role for the user (check Permission levels for teams Permission levels for teams
for more information).
Click on Send Invite.
The invited person will receive an email inviting them to the team. They will need to accept the invitation before becoming a member.

📘
You can click on + Add more emails if you want to invite many team members in a single click.

Via invitation link

Clicking Copy Link will copy the invite link to your clipboard.
Send this invitation link to the person you need to invite.
When they sign up using this link, we'll automatically add them to your team.

📘
You can always click on Reset link to generate a new invitation link. Doing this will revoke invitation from the older link.

Remove a member from your team

If a member in your team no longer requires access to any repository owned by the team, an administrator can remove them from the team.

📘
If you have Automatic Sync with GitHub enabled and SCIM disabled, removing a member from your GitHub organization removes them from the corresponding team on DeepSource as well.

Go to the Dashboard, and on the top left corner, click on the account switcher and then select the team from which you want to remove a member.
Go to the Home tab on the left sidebar.
Go to the Members tab from the list of tabs on the team header.
Find the member you want to remove. Click on the drop down arrow on the right hand side with their role, and select Remove from team.

Transfer ownership of team to another member

An Owner of a team can transfer the ownership of their team to another member via the members page.

Go to the Dashboard, and on the top left corner, click on the account switcher and then select the team whose ownership you want to transfer.
Go to the Home tab on the left sidebar.
Go to the Members tab from the list of tabs on the team header.
Click on Owner to toggle the options and then click on Transfer ownership.
Select the member you want to transfer ownership to from the list of members.
Verify your email address in the next input and fill in rest of the options as per your requirements.
Click on Confirm and transfer ownershipto transfer your team's ownership.

Sync members from VCS provider

About sync

When roles and permissions are changed for any of your team members on your VCS Provider (GitHub, GitLab, or BitBucket), the settings on DeepSource can be updated accordingly by running a Sync.

Running sync

Go to the Dashboard.
Switch to the correct team from the account switcher on the top left corner.
Go to Settings from the central navigation bar.
On the settings page, click on the Access control tab from the left sidebar.
Click on the Sync manually button to sync access settings from GitHub/GitLab/BitBucket.
A modal will inform you that this action cannot be undone. If you still want to continue, click Sync access settings.

Automatic sync with GitHub

By setting up Automatic Sync (currently only available for GitHub), we can sync access settings for you without any manual intervention. Whenever the permissions, or roles are changed on GitHub, whether repository-wide or organization-wide, we are notified via a webhook, and we update the settings automatically. This means that if a user exists on both GitHub and DeepSource, their access settings will automatically be synced from GitHub in the following events:

When you remove an organization member on GitHub, they get removed from the DeepSource team as well.
When you add a new team member on DeepSource that is a member of your organization on GitHub as well, they get added as a repository collaborator on all repositories[1] with the same permission as on GitHub.
When you add, edit permission, or remove a repository collaborator from a repository on GitHub, the same is replicated on DeepSource.

📘
Additional features available only on Enterprise Server

When a user signs-up on DeepSource via GitHub OAuth, they are automatically added to the DeepSource teams with the same role they have on the corresponding GitHub organizations.

When you add an organization member on GitHub, they automatically get added to the corresponding DeepSource team as well.

Released in v3.21.0

Only superuser will be taken to installation page post-signup.

Released in v3.22.0

📘
[1] For large teams i.e. teams having more than 1000 repositories, this sync is done only for the repositories which are activated on DeepSource to avoid GitHub's API rate limit from being exhausted.

Setting up automatic sync

Team Administrators can set up DeepSource to automatically sync access settings from GitHub.

Go to the Dashboard.
Switch to the correct team from the account switcher in the top left corner.
Go to Settings from the central navigation bar.
On the settings page, click on the Access control tab from the left sidebar.
Toggle on the switch next to Automatically sync access settings from GitHub.
Automatic Sync has been set up.