# Permissions and roles ## "Data Inclusion" versus "Permissions" **Data inclusion** controls whose data you see. * If you’re a **Viewer**, your data is **not** included in our insights but you do have access to Multitudes. This is commonly used by managers 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. * Billing is determined by the number of contributors, i.e. the number of people whose data we are processing and showing. ‍**Permissions** controls who can log in, view, and edit things in Multitudes. Here is a table of which permission roles can do what. ### Permission roles 🔐

	No Access	Member	Manager	Owner
Login access	❌	✅	✅	✅
View insights	❌	✅	✅	✅
View their own 1:1	❌	✅	✅	✅
Edit team settings	❌	✅	✅	✅
Install alerts (e.g., Slack)	❌	✅	✅	✅
Install integrations (e.g., Jira)	❌	❌	✅	✅
Add direct reports & view their 1:1s	❌	❌	✅	✅
Edit permissions	❌	❌	❌	✅
Edit billing	❌	❌	❌	✅

{% hint style="warning" %} ‍We encourage all Contributors to have at least some access permissions (Member, Manager, or Owner). This is so that the people whose data is being shared also have access to their own data. Ideally, no one should have “No Access”. 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:

	No access	Member	Manager	Owner
Viewer Data not included	🚫 N/A - by definition, Viewers are always able to "view" the app	Uncommon	✅ Managers who are not active on Github	✅ Managers who are not active on Github, and want to be able to edit permissions and billing
Contributor Data included	⚠️ People should only be in this category during setup, when a manager first adds team members to Multitudes. The manager should then invite everyone via email to log in by changing their permissions from "No access" to "Member"	✅ Team members	✅ Managers who are active on Github	✅ Managers who are active on Github, and want to be able to edit permissions and billing

## **How do I switch between Viewer and Contributor?** Instructions to change a team's Data Inclusion status: ### **Viewer to Contributor** 1. Deactivate the Viewer team member in Multitudes by going to their profile in [Settings](https://app.multitudes.co/teamSettings/teamMember), scrolling to the bottom, and clicking the red `Deactivate` button. 2. Add the team member to your organization on GitHub. With GitHub Teams sync turned on, this should create the user in Multitudes. 3. Give this new user login access by finding them in the [Team Members table](https://app.multitudes.co/teamSettings/teamMember), and clicking the `No Access` dropdown in the Permissions column. Select a different permission to re-invite them into the app. ### **Contributor to Viewer** 1. Remove the team member from all team(s) in GitHub. With GitHub Teams sync turned on, this should remove that team member from Multitudes too. 2. Invite the team member into Multitudes by clicking the `Invite users +` button on the [Settings > Team Members](https://app.multitudes.co/teamSettings/teamMember) page. ## Watcher role Anyone with access to Multitudes (e.g., either Contributors or Viewers) and any permission role (e.g., Member, Manager, or Owner) is automatically [getting alerts](https://docs.multitudes.com/configuration-and-setup/alerts-configuration) for the teams that they are on. The Watcher role simply allows users to get alerts for additional teams that they’re not on. To edit, simply go to the [Settings > Teams](https://app.multitudes.co/teamSettings/team) page. The eye icons at the far right of each team row control whether or not the user is watching that team.