Launch onboarding

This is the ordered journey to get a Managed Service Provider (MSP) live on Conduit: from signing up to having your first customer’s users calling vendor tools through the gateway. It is the map, not the detail — each step links to its own guide.

If you just want to see Conduit work end to end as fast as possible, the Getting Started quickstart is the shortest path. Use this guide when you are taking an MSP all the way to launch and want the full sequence and a go-live checklist.

How to use this guide

Work the steps in order. Each step is a short description plus a link to the guide that walks it in detail. Steps marked optional can be skipped for a minimal launch and added later.

The path to launch

1. Create your MSP organization

Sign up and create your MSP organization. You authenticate through your identity provider; there is nothing to install. See MSP onboarding for the build-out detail.

2. Activate your subscription

A free 14-day trial of the full platform starts automatically when you sign up. Hosted signup asks for a card; there is no charge during the trial, and you can cancel any time. Self-hosted deployments can skip the card field. Conduit is one flat plan — every feature is included from day one. See Billing & plans.

3. Connect your vendor tools

Connect the vendor tools your MSP uses (RMM, PSA, documentation, security, and more) so their capabilities are available through Conduit. Most vendors take an API key; a few use OAuth. See Vendor connections for the catalog, credential scopes, and how to connect each one.

4. Connect an AI client

Point an MCP client at your Conduit endpoint and sign in once. Conduit works with any MCP-compatible client — Claude Desktop, Claude Code, Cursor, Cline, Continue, and more. See Connecting an AI client.

5. Set up your team and access

Invite your technicians, assign roles, and scope which vendors and tools each role can reach (deny-by-default is recommended). See MSP onboarding for team setup and tool allowlists, and Permissions for the role model.

6. Auto-provision users with SCIM (optional)

If you manage identity centrally, connect your identity provider (Entra ID, Okta, JumpCloud, or Google Workspace) to provision users and teams automatically. See SCIM provisioning.

7. Onboard your first customer

Create your first customer organization underneath your MSP, wire up the customer’s vendor access, and invite the customer’s owner. See Onboarding a customer.

8. Verify you are live

Make a test tool call from your AI client against a connected vendor, confirm real data comes back, and check that the call appears in your audit log. See Monitoring your tenant for the usage dashboard, vendor health, and audit log.

Go-live checklist

• MSP organization created and subscription active (trial or paid).
• Required vendor tools connected and validated.
• At least one AI client connected and signing in.
• Team invited; roles and tool allowlists set.
• (optional) SCIM provisioning connected.
• First customer organization created and its vendor access wired.
• A test tool call returns real data and appears in the audit log.

Moving around the org portal

In the signed-in sidebar, Connections, Access, and Org Settings collapse and expand. That choice is remembered in this browser, and the group for the page you are on stays open.

Search (under your email, or ⌘K on a Mac / Ctrl+K on Windows and Linux) filters settings and the other pages in the shell. Press ? for the full shortcut list. The labels use ⌘ or Ctrl based on your computer.

Where to go deeper

• MSP onboarding — the comprehensive build-out reference for every step above.
• Per-integration walkthroughs — step-by-step guides for connecting a specific vendor, getting the credential from the vendor’s own portal, screen by screen. See the Integration walkthroughs section in the sidebar.