Permissions and roles

Learn about permission roles and data inclusion rules in Multitudes.

"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

Here are our recommended settings:

A table showing recommended setting combinations for for data inclusion and permissions.

There are four permissions - no access, member, manager, and owner.
There are two data inclusion levels - viewer (data not included), and contributor (data included).

If a user has no access, then they can't be a viewer - by definition, Viewers are always able to "view" the app. If they are a contributor, ⚠️ 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”.

Member + Viewer is uncommon.
Member + Contributor is recommended for team members.

Manager + Viewer is recommended for managers who are not active on GitHub.

Manager + Contributor is recommended for managers who are active on GitHub.

Owner + Viewer is recommended for managers who are not active on GitHub and want to be able to edit permissions and billing.

Owner + Contributor is recommended for managers who are active on GitHub and want to be able to edit permissions and billing.
Recommended settings

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, 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, 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 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 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 page. The eye icons at the far right of each team row control whether or not the user is watching that team.

Screenshot of Settings > Teams page

Last updated

Was this helpful?