Activate a workstation on SaaS
Use this guide to activate your workstation on a CodeTogether AI SaaS tenant. You'll open the setup link your administrator sends, follow the steps for your IDE, and confirm the workstation is connected.
- Deployment: SaaS
Before you begin
You need all of the following:
- A setup link from your administrator: The link carries an activation code that connects your workstation to your tenant. Ask your administrator if you do not have one.
1. Open the setup link
Open the setup link your administrator sent in a browser. What you see depends on whether the full link arrived intact:
- You land on Workstation Setup: The activation code arrived correctly. Go to step 2.
- You see a page that asks for a setup link: The activation code was stripped from the URL. This happens when a chat or email client removes URL fragments — the part of a link after
#. Paste the full original link into the field on that page, including the#and everything after it. If you cannot retrieve the full link, ask your administrator to send it again.
2. Follow the steps for your IDE
Workstation Setup has a tab for each supported editor. Select the tab that matches the editor you use and follow the steps it shows.
The following table lists the available tabs:
| Tab | Use it for |
|---|---|
| JetBrains | IntelliJ IDEA, GoLand, PyCharm, WebStorm, and other JetBrains IDEs |
| VS Code-based | Visual Studio Code, Cursor, and other VS Code-compatible editors |
| Visual Studio | Microsoft Visual Studio |
| Eclipse | Eclipse IDE |
| Others | Editors not in this table, or command-line AI agents and MCP (Model Context Protocol) clients |
Use Others when you do not use one of the supported IDEs, or when you work primarily through tools such as Claude Code, Codex CLI, or Copilot CLI. The Others path configures capture at the user level, so it does not require an IDE or a repository to be open.
If you use more than one editor, run setup for each one. A developer who completes setup for only one of two editors captures only that editor's sessions.
3. Confirm the workstation is connected
After setup, confirm activity is reaching the portal:
- Make a commit, or run an AI session.
- Ask your administrator to confirm you appear on the developer roster in the portal.
Activity does not appear instantly — processing runs asynchronously, so allow a few minutes before treating an empty view as a problem. See No activity appears for a developer if nothing arrives after that.
Troubleshooting
The setup link takes you to a page asking for a link
A chat or email client stripped the URL fragment that carries the activation code. Copy the full original link and paste it into the field on that page. The activation code is the part after #; without it the page cannot connect your workstation to your tenant.
Setup completed but no activity appears in the portal
Confirm setup ran for each editor you use. A developer using two editors who ran setup for only one shows only that editor's sessions.
If you work with command-line AI agents, confirm the Others path ran on your workstation — the IDE tabs do not configure agent-level capture.
If this doesn't fix it
Contact your administrator or support with all of the following. Tickets missing these take longer to resolve:
- The verbatim error message, if any.
- Your editor or AI tool and operating system.
- Which tab you used on Workstation Setup, or whether you used the Others path.
Related
- Onboard a developer — the administrator's view of the setup flow, including the Others path for command-line tools.
- Set up CodeTogether AI SaaS — the full admin journey that produced the setup link you received.
- No activity appears for a developer — diagnosing missing activity after setup.
- Members and developers — how your workstation identity connects to captured activity.