# Adding Users & Teams You can add your teams and team members automatically via [GitHub Teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams) sync, or manually add your team in our settings page.


Github Teams Sync	/pages/lr9BNdyeJCmQYpftLSfC#automatically-adding-team-members-via-github-teams-sync
Manually adding a team	/pages/lr9BNdyeJCmQYpftLSfC#manually-add-a-team
Manually adding a team member	/pages/lr9BNdyeJCmQYpftLSfC#manually-add-a-team-member

## Enforcing a login option Multitudes allows for login via Google, GitHub, Microsoft, or email and password. To enforce one of these options for your organization, contact . {% hint style="warning" %} Login is enforced based on your organization domain (e.g., @multitudes.com). If you invite a user to your organization via an external email address (e.g., @gmail.com), we won’t be able to enforce their login option. {% endhint %} ## How to give team members login access to Multitudes Login access is a question of permissions. While this is not related to [data inclusion](/configuration-and-setup/permissions-and-roles.md) (i.e., either Viewers or Contributors can be given login access), it does depend on it! To provide access for a... * **Viewer** - go through the flow to [manually add a new team member](/configuration-and-setup/adding-users-and-teams.md#manually-add-a-team-member) (steps just below) * **Contributor** - you had the option to provide login access when [manually adding a new team member](#manually-add-a-team-member) as a Contributor if you filled in the email address when prompted. If you did not include an email, you can change it from the [Settings > Team members](https://app.multitudes.co/teamSettings/teamMember). (See image below) The new Contributor that was added will start with a **No access** flag under their name. Go to the Permissions column, click the arrow, and then select a different permission (e.g., **Member**, **Manager**, or **Owner**). After you do this, you’ll see an **Invite Pending** flag under their name. ![Screenshot of Settings Team Member table, highlighting the location of the "No access" label and permission setting.](https://cdn.prod.website-files.com/610c8a14b4df1ae46b1a13a3/654289b68dce15a9bc6c8f39_4.png) In either case (i.e., once you’ve manually added a new Viewer or Contributor with email, or edited an existing person’s permission to something with access), the person will receive an invite email, and can just click the link in that email to login. {% hint style="warning" %} The invite email will expire after 7 days. You can resend the invite by going to [Settings > Team members](https://app.multitudes.co/teamSettings/teamMember), finding that team member, and clicking the `...` menu on the right of their row, and selecting “Resend Invite”. {% endhint %} ## Automatically adding team members via **GitHub Teams sync** For folks who use [GitHub Teams](https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams), you can automatically keep your teams on Multitudes in sync. This automatically brings in team members, and mirrors the team structure you've set up in GitHub. A few important notes when setting up the Github Team sync: * If you already have teams set up in Multitudes, and then turn on the sync, this will replace your existing teams configuration. * Editing teams is disabled when the sync is turned on. You will not be able to go into a specific team to add or remove team members. This should all be handled in GitHub so you have a single source of truth for team structures. * Anyone that the sync brings in will show up in Multitudes as a Contributor. This may impact [billing](/account-management/billing-and-payments.md). Since the purpose of GitHub Teams Sync is to keep your teams data in sync with your team structure in GitHub, these contributors can not be turned into Viewers to be excluded from the data (manual tweaking of the teams would defeat the purpose of the sync). * The sync will not bring in someone who previously was deactivated. If a team member was previously on Multitudes, and you deactivated them from their individual team member settings, we will not make them re-appear in Multitudes even if they get updated in your GitHub Teams. * The sync will not bring in someone who was previously a [Viewer](/configuration-and-setup/permissions-and-roles.md). It will not convert Viewers to Contributors, but it will give them the [Watcher](/configuration-and-setup/permissions-and-roles.md#watcher-role) role for the team(s) where they have data. E.g. Let's say Pat is a Viewer. The Multitudes app runs a GitHub Teams sync, and finds out that Pat on Team Security and Team Platform in the organization's GitHub Teams. Rather than turning Pat into a Contributor, the sync will simply make Pat a Watcher on those 2 teams and keep him as a Viewer. ### **Follow the below instructions to set-up the sync for the first time:** 1. On the Multitudes app, go to [Settings > Teams](https://app.multitudes.co/teamSettings/team) 2. Click the button “Sync with GitHub Teams”

3. On the next page, you will be shown a list of your teams set-up in GitHub. First, select which you want to keep synced. Second, click "Continue". \ \ A few things to consider as you choose teams: * We will only sync the teams that you check in this step. Unchecked teams are excluded from Multitudes. However, if a parent team is checked but its sub-teams are not, members of those sub-teams will still be included as part of the parent team. * Keeping a team un-checked and un-synced does not mean you can then manually configure that team! The automatic sync entirely replaces your existing team configuration; the idea is that GitHub becomes the single source of truth for teams. These selectors just scope which subset of data from your GitHub Teams you want to see in Multitudes. * You can also check “Auto-sync new GitHub Teams from now on” at the bottom of the list. This means, “from now on” any new teams created in Github after this set-up will be added (i.e., any individual teams you un-checked on this page will not be automatically included later, even if this last option to “Auto-sync new GitHub teams from now on” is checked) * When a team is synced and you delete that team on GitHub, we’ll also automatically remove that team in Multitudes as well. Note that team members will not be removed when their team is deleted, unless they are in no other teams after the team deletion.

4. On the next page, we’ll show you if this first set-up sync resulted in any new or removed Contributors, and therefore the [billing](/account-management/billing-and-payments.md) impact, as well as if it resulted in any changes to your [Linear](/integrations/linear.md) or [Jira](/integrations/jira.md) integrations. Click the "Confirm" button to proceed.

5. Once finished, at the top of the Teams page, you’ll see a checkbox indicating that you’re successfully synced with GitHub (you can also un-check to stop syncing entirely, across all teams)! Once sync is set-up, this is what will happen: * Changes to your team should be reflected in \~5 minutes * People with [Owner permissions](/configuration-and-setup/permissions-and-roles.md) will receive an email: (1) After the initial sync set-up and (2) On an ongoing basis, whenever we detect changes that result in new or removed Contributors * This page will only show you the teams that are synced. Any teams not synced can be added to the sync by clicking the prompt at the bottom

With sync turned on, you can not convert between Contributors ↔︎ Viewers manually via the Multitudes app. This can be managed in GitHub. If you have any issues, don't hesitate to contact us at `support@multitudes.com`. ## **Manually add a team** 1. On the Multitudes app, go to [Settings > Teams](https://app.multitudes.co/teamSettings/team) 2. Click the button “Add team +”

3. In the resulting pop-up: 1. Name your team 2. Select team members from GitHub to add to this team (you're limited to selecting team members who are already on our app; to manually add a team member to the app, see the next section) 3. For team members already on our app with [Manager or Owner permissions](/configuration-and-setup/permissions-and-roles.md), we will detect this automatically, and you can create 1:1 relationships here as well (don’t worry you can always create these later in the My 1:1s page of the application) 4. Click to "Confirm"

## **Manually add a team member** 1. On the Multitudes app, go to [Settings > Team members](https://app.multitudes.co/teamSettings/teamMember) 2. Click on the “Invite users +” button (part 1) and choose whether you’d like to add them as a **Contributor** or **Viewer** (part 2), from a [data inclusion](/configuration-and-setup/permissions-and-roles.md) perspective

3. In the resulting pop-up, if you’d earlier selected to add: * **Viewers** (not shown) - simply add people’s email addresses * **Contributors** (image shown below) - we show you a list of contributors from your connected GitHub that aren’t currently in the Multitudes app. Once you check someone’s GitHub username, an email field will show up at right. If you leave this blank, their data will be incorporated into our insights, but they themselves will not be able to access the app, i.e., **No Access** [permissions](/configuration-and-setup/permissions-and-roles.md). If you fill this in with their email, they will be sent an invite to access the app with default **Member** permissions (you can change permissions later from the [Settings > Team members](https://app.multitudes.co/teamSettings/teamMember) page to Manager or Owner permissions).

{% hint style="info" %} If you’re adding **Contributors**, clicking the “Select contributors” button in the blue banner at the top of the page (which appears whenever we detect new GitHub contributors not yet on Multitudes, see example in the screenshot for Step 1 above) will directly take you to the same Step 3 as if you’d clicked “Invite users +” and then selected **Contributors**. {% endhint %} ## Deactivating a team member {% hint style="info" %} **Only Owners can deactivate team members.** {% endhint %} When you deactivate a team member, Multitudes will no longer show data for this person from this point onwards and the team member will lose access to Multitudes (if they currently have access). To do this, go to the [Settings > Team Members](https://app.multitudes.co/teamSettings) and look up the team member you want to deactivate. Go to their profile and at the bottom, click the Deactivate button. Then when the modal pops up, click "Deactivate `{name}`" to confirm.

#### Expired invite If the user has an expired invite, you will need to cancel their invite first before you can deactivate. To do this, find the team member in the [Settings > Team Members page](https://app.multitudes.co/teamSettings). Click the 3 dots at the end and cancel invite. Once this is done, you can deactivate per instructions above.\ \ If the user was invited as a viewer, cancelling their invite will automatically deactivate them.

#### View deactivated users and reactivate them You can view deactivated team members by setting the "Status" filter to "Deactivated" in the Team Members page. To reactivate a team member click the three dots in their row and then click "Reactivate". {% hint style="warning" %} **If you have Github Teams Sync enabled:** * Team members will automatically be deactivated when they are removed from all synced teams in Github. * You cannot currently reactivate your team members via Multitudes. Please contact for help. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.multitudes.com/configuration-and-setup/adding-users-and-teams.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.