End-to-end onboarding walkthrough

This page walks an MSP from “I just signed up” to “my first customer’s first agent is making real tool calls” — in one ordered pass. Each step has a one-line summary plus a link to the in-depth guide for that step. If you only have 30 minutes, this page is enough; if you want the depth, follow the links as you go.

Before you start

You need:

• A login for the email you’ll use as the MSP owner.
• A card at hosted signup. A 14-day free trial of the full platform starts automatically — there is no charge during the trial, and you can cancel any time. Self-hosted deployments can skip the card field. You do not need to visit the billing page to begin.
• API credentials for at least one vendor you want to connect — the credential is whatever the vendor’s portal calls an “API key,” “personal access token,” or “client credentials” pair. The per-vendor walkthroughs tell you exactly where to get them.
• (If you’ll onboard a customer in this same session) the customer’s name and the email of their owner — the person who will administer the customer organization once it’s set up.

Time to complete: ~30–60 minutes the first time. Subsequent customer onboardings take 5–15 minutes once the MSP-side setup is done.

---

Part 1 — Stand up your MSP organization

1. Sign up and create your MSP organization

Go to https://conduit.wyre.ai/signup, enter your business name. If the hosted trial requires a card, add one when prompted, then complete sign-in. There is no charge during the 14-day trial, and you can cancel any time. Conduit provisions your MSP organization using the name you entered and lands you on the dashboard.

You’re now the owner of the MSP organization. There’s nothing to install — Conduit is a hosted gateway.

See MSP onboarding for the discovery questions (vendor inventory, customer profile, identity provider) you’ll want answered before adding teammates.

2. Connect your first vendor (MSP-organization level)

Vendors connected at the MSP-organization level are usable by your own technicians. (Vendors connected for an individual customer come later, in Part 2.)

1. Open Connections (/org/catalog).
2. Pick the vendor. API-key vendors show a credential form; you paste the key and click Connect. OAuth vendors (Xero, QuickBooks Online, Calendly) redirect you to the vendor’s consent screen; you authorize and the vendor sends you back to Conduit with the token.
3. Conduit encrypts the credential at rest and runs a health check. A green status on the Connections page means the connection is ready.

Where the per-vendor credential comes from (Atera “Admin → API,” HaloPSA “Configuration → Integrations → HaloPSA API,” etc.) is documented in the per-vendor walkthroughs and the Vendor connections guide.

3. Activate your subscription (any time during the trial)

You do not need to do this before connecting your first vendor. Sign-up puts your organization on the plan and starts a free 14-day trial automatically, so the Connections page above is available immediately. Visit Billing whenever it suits you during the trial.

Visit Billing (/org/billing). Conduit ships on a single flat plan:

• $39/month per billable seat — every team member (human or agent service-client) is a billable seat, at the same per-seat rate. There is no separate organization base fee.
• The first two agent (service-client) seats are free with the base; agent billing starts at the third agent seat. Human seats are unaffected — they bill from seat 1.

A free 14-day trial of the full platform starts automatically. The card collected at signup is not charged during the trial; update it from Billing if needed.

Why this step is deferrable, and when that would stop being true. Paid surfaces — the Connections page included — are gated on the organization’s plan, not on you having visited Billing. Sign-up creates every organization already on the plan (plan = 'conduit'), so the gate admits you from the moment the organization exists. If sign-up ever stops putting new organizations on the plan at creation, this step becomes a real prerequisite again and must move back ahead of Step 2.

See Billing & plans for the rate-change notice policy, payment-method updates, and dunning/recovery behavior if a payment fails.

4. Connect an AI client to your MSP organization

Conduit speaks the Model Context Protocol — any MCP-capable AI client connects. Most common are Claude Desktop and Claude Code; the same pattern works for Cursor, Cline, Continue, and others.

Claude Desktop (edit claude_desktop_config.json):

{
  "mcpServers": {
    "conduit": {
      "url": "https://conduit.wyre.ai/v1/mcp"
    }
  }
}

Claude Code (one CLI command):

claude mcp add --transport http conduit https://conduit.wyre.ai/v1/mcp

First use opens your browser for sign-in. After sign-in, the JWT is cached locally and refreshed automatically — you sign in once per device.

See Connecting an AI client for the client-by-client setup (including Microsoft Copilot Studio) and Supported clients for the full list.

5. Verify your MSP-side setup works end-to-end

Before moving to customer onboarding, prove that the MSP-organization-level setup actually works. From your AI client:

• Make one test tool call against the vendor you connected in Step 2 (“List my active Atera alerts,” “Show me my open HaloPSA tickets,” “Pull this week’s RocketCyber incidents,” etc.).
• Open the audit log (/org/audit). The call you just made should appear with the correct user, vendor, tool name, and timestamp.
• Open the vendor health view on the Connections page. The vendor you connected should show green.

If any of those three doesn’t land, fix it now before continuing — the customer-onboarding steps below assume a working MSP-side setup.

See Monitoring your tenant for the usage dashboard, vendor-health detail, and audit-log filters.

---

Part 2 — Onboard your first customer

Conduit is built for MSPs serving their own customers. Each customer the MSP onboards is a separate organization underneath the MSP — fully isolated from every other customer, with its own users, vendor connections, and audit log, but administered by the MSP.

6. Create the customer organization

From the dashboard:

1. Open Customers (/org/customers) and click + Add Customer. The New Customer wizard opens.
2. Step 1 — Customer. Enter the customer’s organization name. Conduit generates a URL slug from the name; adjust it if you prefer a different one. The slug becomes the customer’s MCP endpoint URL: https://conduit.wyre.ai/v1/mcp/<your-slug>/<customer-slug>.
3. Step 2 — Admin. Enter the email of the person who will own the customer organization. They’ll receive an invitation by email and set their own password via the link.
4. Step 3 — Review. Confirm the summary and click Create customer.

Conduit creates the customer organization, sets you as the interim owner until the invitee accepts, and sends the owner invitation email.

See Onboarding a customer for the per-field detail of the New Customer wizard plus what happens immediately after creation.

7. Wire up the customer’s vendor access

The customer organization is live but no vendor tools are exposed yet. There’s no dedicated onboarding wizard — you connect vendors by switching into the customer.

From /org/customers, click Manage on the customer’s row. This puts you into acting-as mode on the customer’s own organization — an acting-as banner confirms you’re operating on their behalf.

Open Connections → Catalog (/org/catalog) and click Connect on the vendor you want. This opens a one-step connect page (/connect/<vendor-slug>) — an API-key form or an OAuth redirect, depending on the vendor. That’s the per-user path: each person connects their own account, and their tool calls show up under their own identity in the vendor’s audit log.

Two other patterns live on different surfaces, not in the Catalog flow:

• Shared org-level credentials — connect from Connections (/org/catalog) as an admin action; every user in the customer org goes through the one set of credentials you provide.
• Self-hosted (via a Tunnel) — a separate surface, Connections → Tunnels (/org/tunnels). The customer runs the vendor’s MCP server on their own infrastructure, reached through a small Conduit Tunnel — credentials never leave their network. See the Tunnel quickstart for the deploy steps.

Connecting a vendor doesn’t grant tool access by itself. Set the tier — and, optionally, a specific tool allowlist — from the connection’s Access editor. See Managing access.

8. Invite the customer’s first users

The customer’s owner (the person you invited in Step 6 above) signs into the customer organization via the email link, sets their password, and lands on the customer dashboard. From there they invite their own team:

• From the customer’s perspective (the customer admin signs in at https://conduit.wyre.ai/v1/mcp/<your-slug>/<customer-slug>): open Members (/org/members) → + Invite → enter the team member’s email and role (admin or member) → send. The teammate receives an email link.

Alternatively, as the MSP, you can invite on the customer’s behalf: switch into the customer (Manage from /org/customers, which puts you in acting-as mode) and use their own Members page (/org/members) the same way.

See Permissions for the role model and what each role can do.

9. The customer’s first agent session

The customer’s users connect their own AI client to the customer’s MCP endpoint (note: this URL is different from the MSP’s MCP endpoint — it’s the customer-specific one from Step 6):

Claude Desktop:

{
  "mcpServers": {
    "conduit": {
      "url": "https://conduit.wyre.ai/v1/mcp/<your-slug>/<customer-slug>"
    }
  }
}

Claude Code:

claude mcp add --transport http conduit https://conduit.wyre.ai/v1/mcp/<your-slug>/<customer-slug>

On first use, the customer’s user signs in with their own credentials (set in Step 8). After sign-in, they can ask Claude (or any MCP-capable client) to perform vendor actions — “What tickets did Acme submit this week?” or “Run the threshold-monitor script on Acme’s primary server” — and the call flows through Conduit’s gateway, with the customer’s per-tool access (Step 7) enforced.

10. Verify the customer is live

• The customer’s user makes one tool call from their AI client.
• The MSP switches into the customer (Manage from /org/customers, acting-as) and opens Audit Log (/org/audit) to confirm the call appears with the correct user, vendor, tool, and timestamp.
• The customer’s Usage tab (/org/customers/<id>/usage, reachable from the reseller side without switching) shows tool-call volume against the customer’s allowlisted vendors.

If all three land, the customer is live.

---

Part 3 — Where to go after launch

Once one customer is live, the same pattern repeats per customer:

• Repeat Steps 6–10 for each subsequent customer. The MSP-side setup (Part 1) only runs once; each new customer is ~10–15 minutes of wizard time.
• Set up identity provider auto-provisioning (optional) — SCIM provisioning connects Entra ID / Okta / JumpCloud / Google Workspace to Conduit so new MSP team members are provisioned and deprovisioned automatically.
• Watch the dashboards — the Monitoring guide covers the usage dashboard, vendor-health alerts, and audit-log filtering.

The full ordered map (MSP → customer → ongoing administration) lives in the Launch onboarding guide; this walkthrough is the single-page version of that journey.

---

Go-live checklist

For the launch-day eyeball: every box ticked = your MSP and your first customer are live.

MSP-organization side:

• MSP organization created (Step 1).
• At least one MSP-org-level vendor connected and green (Step 2).
• Subscription active — trial or paid (Step 3; the trial is automatic, so this is already ticked unless you have let it lapse).
• At least one AI client connected to the MSP-org MCP endpoint (Step 4).
• One MSP-side tool call succeeded and appeared in the audit log (Step 5).

Customer side (per customer):

• Customer organization created (Step 6).
• At least one vendor connected for the customer (Step 7).
• Customer owner invited and accepted (Step 6 + Step 8).
• At least one customer-side user with a role (Step 8).
• First customer-side AI tool call succeeded and appeared in the customer’s audit log (Steps 9 + 10).

---

Product gaps surfaced during this walkthrough

Two concepts don’t currently exist as first-class Conduit terms. Documenting both here for product-team visibility:

“Workspace” — not a Conduit concept

The only matches in the codebase for workspace are generic (“workspace name” in auth-flow comments, “reseller workspace” as loose marketing language) — not a product abstraction. The canonical Conduit term for what a single MSP or customer occupies is organization. This walkthrough uses organization throughout.

“Entity mapping” — feature not built

There are no references to entity-mapping anywhere in the Conduit codebase. This walkthrough does not include a step for entity mapping, because the feature does not currently exist.

---

Where to go deeper

• Launch onboarding — the ordered map with optional steps and SCIM/handoff coverage.
• MSP onboarding — discovery questions, vendor inventory, and the team-roles model.
• Onboarding a customer — per-field detail on the New-Customer wizard and how to manage a customer day-to-day via acting-as.
• Vendor connections — per-vendor catalog, plus the per-vendor walkthroughs.
• Connecting an AI client — client-by-client setup for Claude Desktop, Claude Code, Cursor, Cline, Continue, and others.
• Permissions — the role model (owner / admin / member) and what each role can do.
• Subtenant Model — the underlying reseller → customer → sub-customer hierarchy and transitive admin.
• API reference — every step above has an API equivalent for teams automating provisioning.