The Connect app groups work into Send, Measure, and Build. These labels organize the existing workspace pages: Send manages content and delivery, Measure shows learning activity and evidence, and Build contains integration tools. Choose the correct workspace before creating credentials or changing a delivery path.
Find a task
The links below open the signed-in app. They retain the existing /dashboard URLs; you may be asked to sign in first.
| What you want to do | Navigation | Direct link |
|---|---|---|
| Check workspace activity and next steps | Send → Overview | Open Overview |
| Upload a package or manage course versions | Send → Courses | Open Courses |
| Manage customers and organizations | Send → Organizations | Open Organizations |
| Review delivery paths | Send → Delivery | Open Delivery |
| Create or manage a dispatch | Send → Dispatches | Open Dispatches |
| Review available LMS connections | Send → Connections | Open Connections |
| Review sessions, completions, and activity trends | Measure → Activity | Open Activity |
| View learner reports and exports | Measure → Reports | Open Reports |
| Inspect learning statements | Measure → xAPI Stream | Open xAPI Stream |
| Create, rotate, or revoke an API key | Build → API keys | Open API keys |
| Manage webhook endpoints and delivery history | Build → Webhooks | Open Webhooks |
| Inspect partner API request traffic | Build → Request logs | Open Request logs |
| Explore integration contracts | Build → Explorer | Open Explorer |
| Find available AI publishing tools | Build → AI Builders | Open AI Builders |
The Connect logo returns to Send → Overview. Account and workspace utilities are separate from the environment navigation: Settings, Account, and Support keep their existing destinations.
Copy the workspace identifier and API key
Open Build → API keys and use the Connect credentials card. Its current identifier label is Account ID. This is the workspace identifier used as tenant_id in API requests and CONNECT_TENANT_ID in environment configuration; it is not the ID of an individual user or an API key.
Select New API key to create a key with the appropriate scope. Copy the secret when it is revealed and store it server-side. See API key security for scopes, rotation, and authentication examples.
Check LIVE and TEST before acting
The LIVE/TEST control selects the credential and delivery mode within the current workspace. It does not create a separate workspace or a separate data plane. Confirm both the workspace and mode before creating keys or webhook endpoints, launching content, or reviewing evidence.
Connect-minted API keys use ac_live_… or ac_test_… prefixes. Use the key and endpoint mode appropriate to your workflow. TEST credentials do not enable all API families: Skills, capability, graph, CALE, and xAPI statement APIs currently reject TEST credentials with 403 TEST_MODE_UNSUPPORTED, and the corresponding dashboard surfaces show an unavailable state. Changing mode does not bypass a role or subscription requirement.
Use an isolated workspace and a non-production deployment for automated test fixtures. The API key security guide explains the evidence-separation limits.
Understand availability and permissions
Navigation helps you find a feature; it does not grant access. Workspace membership, role, subscription, capability availability, and mode still determine which actions are available. For example, Measure → Skills, Ask, and Value have capability requirements. A listed connection does not mean every provider can be activated: follow the availability state and setup requirements shown on the page.
Platform administration is a separate authorized surface. Customer workspaces do not receive platform administration access by opening an admin URL. If a task is unavailable, confirm the selected workspace and ask your workspace owner or Support about the required access.
If your navigation still looks different
The updated shell and legacy navigation can coexist during rollout. You may still see Integrations, Developer/API, Learner Reports, or Dispatch instead of the newer grouped labels. Open the direct links above to reach the same underlying pages: Build → API keys and Build → Webhooks are tabs of the existing Integrations page, Measure → Reports uses the existing reports URL, and Send → Dispatches uses the existing dispatch URL.
This navigation update does not add /send, /measure, or /build URL prefixes. Existing bookmarks, API routes, launch links, and integration contracts retain their meaning. Do not rewrite an LMS launch URL or change an API base URL merely because the navigation labels changed.