Data inclusion controls whose data you see.
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:
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.
For folks who use GitHub Teams, you can automatically keep Multitudes teams in sync with the teams on Github!
A few important notes when setting up the Github Team sync:
Follow the below instructions to set-up the sync for the first time:
Click the button “Sync with GitHub Teams”
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". Note:
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 impact, as well as if it resulted in any changes to your Linear or Jira integrations. Click the "Confirm" button to proceed
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:
Click the button “Add team +”
In the resulting pop-up:
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 perspective
In the resulting pop-up, if you’d earlier selected to add:
Note: 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.
Login access is a question of permissions. While this is not related to data inclusion (i.e., either Viewers or Contributors can be given login access), it does depend on it! To provide access for a...
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.
Note that the invite email will expire after 7 days. You can resend the invite by going to Settings > Team members, finding that team member, and clicking the ... menu on the right of their row, and selecting “Resend Invite”.