LogoLogo
  • Getting started
    • Welcome
    • Introduction to Multitudes
    • How Multitudes Works
  • Configuration & Setup
    • Setup: Integration Permissions
    • Permissions and roles
    • Adding Users & Teams
    • Configuring your Team
    • User Linking
    • Configuring Working Hours
    • Customize Work Categories
    • Alerts Configuration
    • Customize Targets
  • Metrics & Definitions
    • Multitudes Insights
    • Our Approach to Metrics
    • Process Metrics
      • Flow of Work
        • Change Lead Time
        • Coding Time
        • Review Wait Time
        • Editing Time
        • Deploy Time
        • PR Size
        • Focus Time
      • Value Delivery
        • Deployment Frequency
        • Merge Frequency
        • Types of Work
        • Feature vs Maintenance Work
      • Quality of Work
        • Change Failure Rate
        • Mean Time to Recovery
        • Mean Time to Acknowledge
        • Number of Pages
        • Deployment Failure Rate
    • People Metrics
      • Wellbeing
        • Out-of-Hours Work
        • Page Disruptions
        • Meeting Load
      • Collaboration
        • PR Participation Gap
        • PR Feedback Given
        • PR Feedback Received
        • Feedback Flows
    • Deployment Metrics
  • Integrations
    • Deployments API
    • GitHub Actions
    • Google Calendar
    • Outlook Calendar
    • Jira
    • Linear
    • Opsgenie
    • PagerDuty
    • Slack
  • Knowledge base
    • Annotations
    • Exporting your data
    • Types of Alerts
      • Daily Blocked PRs alert
      • Trend Summary alert
      • Multitudes AI Coach
      • 1:1 Prompts
      • Annotations alert
    • Troubleshooting Missing Commits
    • Bot Activity
    • Collaborative PRs & All PRs Toggles
  • Account Management
    • Billing & Payments
    • Security & Privacy
Powered by GitBook

© Multitudes 2025

On this page
  • "Data Inclusion" versus "Permissions"
  • How do I switch between Viewer and Contributor?
  • Viewer to Contributor
  • Contributor to Viewer
  • Watcher role

Was this helpful?

  1. Configuration & Setup

Permissions and roles

Learn about permission roles and data inclusion rules in Multitudes.

PreviousSetup: Integration PermissionsNextAdding Users & Teams

Last updated 3 months ago

Was this helpful?

"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.

‍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.

Here are our recommended settings:

How do I switch between Viewer and Contributor?

Instructions to change a team's Data Inclusion status:

Viewer to Contributor

  1. Add the team member to your organization on GitHub. With GitHub Teams sync turned on, this should create the user in Multitudes.

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.

Watcher role

Recommended settings

Deactivate the Viewer team member in Multitudes by going to their profile in , scrolling to the bottom, and clicking the red Deactivate button.

Give this new user login access by finding them in the , and clicking the No Access dropdown in the Permissions column. Select a different permission to re-invite them into the app.

Invite the team member into Multitudes by clicking the Invite users + button on the page.

Anyone with access to Multitudes (e.g., either Contributors or Viewers) and any permission role (e.g., Member, Manager, or Owner) is automatically 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 page. The eye icons at the far right of each team row control whether or not the user is watching that team.

Settings
Team Members table
Settings > Team Members
getting alerts
Settings > Teams
Screenshot of Settings > Teams page
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.
Permission roles