> For the complete documentation index, see [llms.txt](https://docs.multitudes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multitudes.com/configuration-and-setup/user-types-data-inclusion-and-roles.md).

# User Types, Data Inclusion, and Roles

Learn about the types of users in Multitudes.

## Bot vs Human user types

**Type** indicates whether a user is a human or a bot:

* **Humans** are what they sound like – human users on teams in Multitudes. You can grant login access to a Human; see the next section for more about "Roles".
* **Bots** are any non-human entities making changes in your codebase, from simple dependency-updating bots like Renovate or Dependabot to agents making more complex changes. Bots cannot log in to Multitudes – they are always a "No access" role type.

Both humans and bots can have their data included in Multitudes if you make them Contributors. For more, see the "Data inclusion" definition in the next section.

## "Data Inclusion" versus "Roles"

**Data inclusion** controls whose data you see in the app and who you get billed for:

* If you’re a **Non-contributor**, your data is **not** included in our insights and there is no charge for your login access. This is commonly used by people who are not very active on GitHub, but would still like to view their team’s data.
* If you’re a **Contributor**, your data is included in our insights. Contributors can be humans or bots. Billing is determined by the number of contributors, i.e., the number of users whose data we are processing and showing.

‍**Roles** controls who can log in, view, and edit things in Multitudes. Only humans can have an access role (Member, Manager, or Owner). Bot users cannot log into Multitudes and so cannot have a role (they never have Multitudes login access). Read on for more about the different permissions available to different roles.

### Roles 🔐

Note that users with the `No Access` role cannot log in and therefore cannot do any of these actions.

<table data-full-width="true"><thead><tr><th width="493.19140625">Action</th><th width="155.54296875" align="center">Member</th><th width="144.0703125" align="center">Manager</th><th width="131.53515625" align="center">Owner</th></tr></thead><tbody><tr><td><strong>Log in and view insights</strong></td><td align="center">✅</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><strong>View their own 1:1</strong></td><td align="center">✅</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><strong>Edit team settings</strong></td><td align="center">✅</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><strong>Install notifications</strong><br><sub>(e.g., Slack)</sub></td><td align="center">✅</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><p><strong>Install integrations</strong></p><p><sub>(e.g., Jira, Linear)</sub></p></td><td align="center">❌</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><strong>Add direct reports &#x26; view their 1:1s</strong></td><td align="center">❌</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><strong>Update Data settings</strong><br><sub>(e.g., setting default percentiles)</sub></td><td align="center">❌</td><td align="center">✅</td><td align="center">✅</td></tr><tr><td><strong>Edit other users' roles</strong></td><td align="center">❌</td><td align="center">❌</td><td align="center">✅</td></tr><tr><td><strong>Edit billing</strong></td><td align="center">❌</td><td align="center">❌</td><td align="center">✅</td></tr></tbody></table>

{% hint style="warning" %}
‍We encourage companies to give all Contributors login access (a role of Member/Manager/Owner).

This is so that the people whose data is being analyzed also have access to their own data – it allows people to use the data to set their own goals, and to add their context to the data with annotations.

Ideally, no one should have “No access” for an extended period. This option is available to allow managers to get set up and familiar with Multitudes before inviting their team in.
{% endhint %}

### Here are our recommended settings:

<table data-full-width="true"><thead><tr><th width="137.30859375" valign="top">Data inclusion</th><th width="290.83984375" valign="top">No access</th><th width="137.671875" valign="top">Member</th><th width="138.76171875" valign="top">Manager</th><th width="141.66796875" valign="top">Owner</th></tr></thead><tbody><tr><td valign="top"><strong>Non-contributor</strong><br>Data not included</td><td valign="top"><em><strong>Human users:</strong></em> Uncommon.<br><br><em><strong>Bot users:</strong></em> All bots have no access.</td><td valign="top">Often used for non-engineers who want to see Multitudes insights – e.g., a delivery lead.</td><td valign="top">✅ Managers who are <em><strong>not</strong></em> active on GitHub.</td><td valign="top">✅ Leaders who are <em><strong>not</strong></em> active on GitHub, and want to be able to edit permissions and billing.</td></tr><tr><td valign="top"><strong>Contributor</strong><br>Data included</td><td valign="top"><em><strong>Human users:</strong></em> ⚠️ Humans should only be in this category during a trial. After that, we recommend making all contributors at least a "Member".<br><br><em><strong>Bot users:</strong></em> All bots have no access.</td><td valign="top">✅ Team members</td><td valign="top">✅ Managers who are active on GitHub.</td><td valign="top">✅ Managers who are active on GitHub, and want to be able to edit permissions and billing.</td></tr></tbody></table>

## **How do I switch between Non-contributor and Contributor?**

If you want to change whose data is included in Multitudes insights, you'll need to change users between Non-contributor and Contributor (data from Contributors is included in insights; data from Non-contributors is excluded from insights – [more above](#data-inclusion-versus-roles)).

**If GitHub team sync is on:**

To add someone as a contributor in Multitudes, add them to a synced team in GitHub.

**If GitHub team sync is off:**

1. Go to [Settings > Members](https://app.multitudes.co/settings/members).
2. Find the profile of the person or bot you want to change.
3. Click into their profile, go to the "Data inclusion" section, and change between Non-contributor and Contributor. Note that this change has a billing impact, because Multitudes charges based on the number of Contributors in the app. [More on our billing page](https://docs.multitudes.com/account-management/billing-and-payments#who-do-i-get-charged-for-on-the-multitudes-app).

<figure><img src="https://3759751588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1eOL1LoKX0USQQUCSepS%2Fuploads%2FGVEML8tDqXMAy1jTOG52%2Fedit-profile-data-inclusion-annotated.png?alt=media&amp;token=3bc444de-591e-4733-83c1-ca3ccba0ec05" alt=""><figcaption></figcaption></figure>

## Watcher role

Anyone with login access to Multitudes (e.g., a role of Member, Manager, or Owner) is automatically [receiving notifications](broken://pages/XIZpYzIy7IeID47L2Mjj) for the teams that they are on. However, sometimes someone wants to get updates for teams they're not on; the Watcher role is for this use case.

The Watcher role allows users to receive notifications for additional teams that they’re not on. To edit, head to [Settings > Members](https://app.multitudes.co/settings/members), click into the profile for the relevant user, find the "Watching" section, and select the relevant teams from the selector.

<figure><img src="https://3759751588-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1eOL1LoKX0USQQUCSepS%2Fuploads%2FvdWSRjqdIiAXTKNRqnfx%2Fedit-profile-watching-annotated.png?alt=media&amp;token=6a4e0511-db3e-4d78-9507-1b82e5efe53f" alt=""><figcaption></figcaption></figure>
