Skip to main content
Ready to get started? Head over to the Macroscope website to configure your account. You’ll be guided through the sign up process outlined below. Within minutes, you’ll have Macroscope integrated into your workflow and running for your team. Click here to sign up on the Macroscope website.

​
Step-by-Step Sign Up Process

1

Install the Macroscope GitHub App

After you click “Sign Up” on the Macroscope website, you’ll be directed to GitHub to install the GitHub Macroscope App.
FAQ: We have a lot of repos, some aren’t active anymore—should I include them in our installation?→ Yes. Inactive repos are fine to include since we only process the last two weeks of commits plus new activity going forward. You can also remove access later if needed.
If your company uses GitHub Enterprise Managed Users, follow this guide to log in to Macroscope.
2

Set Up Subscription

Activate your Macroscope subscription via Stripe.
3

Configure Preferences

You will be asked to share a Product Overview. This helps Macroscope understand your product while backfilling code summaries. You can update this anytime in Settings —> Workspace, which will improve summaries going forward.You will also be asked to share your Weekly Sprint Cadence, so Macroscope knows when your team’s sprints start and end. This affects your Productivity Dashboard as well as determines when your Weekly Email Reports are delivered. You can adjust your sprint cadence anytime in Settings → Weekly Cadence.
4

Connect Jira / Linear Integrations

Some teams use both Jira and Linear as issue tracking systems, others use only one. Connect whichever you use—these integrations provide crucial context for Macroscope, helping it better understand your team’s work and progress.See detailed instructions for how to integrate Macroscope with your issue management systems.
5

Choose Weekly Report Schedule

Macroscope will send you weekly reports summarizing recent activity and highlighting productivity insights. You can subscribe additional teammates to weekly email reports in Settings —> Digest Emails and adjust the delivery schedule in Settings —> Weekly Cadence.
6

Connect Slack

Connecting Slack is a critical step — it unlocks the Ask Macroscope Anything and Code Activity Subscriptions features in Slack.You must be a Slack Admin to install Macroscope’s Slack app, which turns on the integration.If you are setting up Macroscope and are not an Admin for your company’s Slack workspace, we’ll provide you a link to share with your Slack workspace Admin.
FAQ: Who on my team can interact with Macroscope in Slack?Default Slack settings:
  • Anybody in Slack can @mention Macroscope.
  • The first time they do, they’ll be asked to log in to Macroscope. This ensures that only users who have access to GitHub/Macroscope can interact.
  • If someone hasn’t logged in, Macroscope won’t respond.
Optional setting:
  • You can loosen this constraint to allow anybody in Slack to ask questions of Macroscope, even if they don’t have a Macroscope account.
  • This can be a powerful way to help your whole company get better informed about your codebase, code activity, and product.
  • To enable this setting, please contact Macroscope Support.

​
What Happens Next?

That’s it! Once connected, Macroscope will automatically:
  • Start backfilling data from your GitHub repos
  • Send weekly reports summarizing the team’s activity
  • Generate plain-language summaries for commits and pull requests in GitHub
  • Review pull requests for correctness issues and suggest fixes in GitHub
FAQ: What features are limited to Admins?
  • Billing and payments
  • Managing Areas
  • Changing productivity insights settings
  • Changing external contributor settings
  • Configuring email digest recipients
FAQ: How do I make someone an Admin in Macroscope?→ Macroscope inherits permissions from GitHub. Anyone who is an Admin of the linked GitHub organization is automatically an Admin in Macroscope.
FAQ: Who can use Macroscope?Access to Macroscope is inherited from your company’s GitHub membership. Anyone with access to your company’s GitHub organization has access to Macroscope. Permissions and visibility follow GitHub: if someone can see a repo in GitHub, they can ask Macroscope about it.

​
What Should I Do Next?