Skip to main content

Set up CodeTogether AI SaaS

Use this guide to set up a CodeTogether AI SaaS tenant from trial to activity. You'll start a trial, connect GitHub, configure which repositories are captured, send your developers their setup link, and read the first results.

  • Deployment: SaaS
  • Role: Owner, Admin

Throughout these pages, capture means recording development activity — commits, IDE activity signals, and AI-agent sessions — from the repositories and tools a developer has configured. What is captured states the exact boundary, including what is never collected.

If you run the platform in your own environment instead, see Deploy CodeTogether AI on-premises.

Before you begin​

To complete SaaS setup, you need all of the following:

  • An email address: You can sign in with Google or with a username and password.
  • Permission to install a GitHub App in your GitHub organization: You need this to connect source control at the organization level. Without it, capture works but pull-request and merge data are absent.
  • A way to reach your developers: You send them one setup link; email or chat is enough.

1. Start your trial​

  1. Go to the CodeTogether AI portal and select Start trial.
  2. Sign in with Google, or create an account with an email address and password.
  3. Follow the prompts to name your organization. Your tenant is provisioned and you land in the portal.
ScreenshotPortal trial sign-up screen with Google sign-in and email/password options.

Your tenant starts with one default work area that covers the whole organization. You add more focused views after activity arrives.

2. Connect GitHub​

Connecting GitHub adds pull-request and merge-outcome data so the product knows what merged, not only what was pushed.

  1. Go to Settings > Integrations > Source Control.
  2. Select Create from Manifest to provision a GitHub App owned by your organization. GitHub generates the App from a manifest the portal supplies, so you do not register or configure an App on GitHub by hand.
  3. Select Connect to install the App.
ScreenshotSettings page with Source Control selected in the Integrations sidebar, showing the Create from Manifest and Connect actions.

Connect at the organization level rather than per repository. An organization-level App covers all repositories in your GitHub organization automatically, so you do not update it when a new repository is created.

For the full list of what this integration adds, see Connect integrations.

3. Confirm which repositories are tracked​

Which repositories are tracked follows your GitHub connection: an org-wide App install tracks every repository under that organization automatically, and a selected-repositories install tracks only the repositories you chose. Add anything outside that — a repository on a different host, or a whole organization you have not connected through GitHub — as a manual entry.

Review or add entries at Settings > Activity Tracking > Repositories. Select Configure to connect GitHub or add a repository, organization, or name pattern manually. With nothing tracked yet, the page states this plainly rather than capturing silently. This is separate from workstation setup, which is system- and IDE-level and does not need to be run per repository.

4. Onboard developers​

Developers are not invited like members. Their work is captured the moment the AITrax tracker — the program each developer installs on their own workstation to capture their activity — runs on their machine. You send them one link; they handle the rest. Set up your workstation is the developer's view of that installation.

  1. Open Setup in the portal sidebar.
  2. Copy the workstation setup link from the Managers and Admins section.
  3. Send the link to your developers.
ScreenshotSetup page in the portal, sidebar showing Setup selected and the page title visible.
ScreenshotManagers and Admins section, cropped to the workstation setup link and its copy control.

Each developer opens the link in a browser and follows the steps for their IDE. The link carries an activation code as a URL fragment. Some chat and email clients strip URL fragments — if a developer reports landing on a page asking them to enter a setup link, the fragment was dropped and they need the full link, including the part after #. See Activate a workstation on SaaS for the steps the developer follows, and Onboard a developer for the manager-level view of the full onboarding flow.

5. Delegate admins (optional)​

The person who started the trial holds the Owner role and has full control, including billing. If someone else carries day-to-day administration, invite them as Admin before distributing the setup link.

Admin role can manage integrations, onboard developers, and configure work areas. Owners retain sole control over billing and Owner-role changes. To add an Admin, see Invite users to your organization.

Delegating admins is less critical on SaaS than on-premises, because there is no server infrastructure to hand off.

6. Read the results​

As developers complete setup, activity flows to the portal.

  1. Open All Areas to see the full-organization view as the first activity arrives.
  2. After you have enough data to recognize patterns, create work areas scoped by team, project, or a custom combination. See Create a work area.
ScreenshotAll Areas dashboard showing the first developer activity after setup completes.

Work areas are far easier to scope after real data is present. The default company work area is a good starting point and requires no configuration.