Growing your team on Conduit
This guide picks up where Getting started leaves off: your organization exists, one vendor is connected, and an AI client is making tool calls. It covers the next steps for growing that into a working team setup — inviting people, connecting more of your stack, and controlling who can do what.
If you’re setting up Conduit to resell to your own customers rather than for your own team, see MSP Onboarding instead — that guide covers the customer-provisioning layer this one doesn’t.
Invite your team
Section titled “Invite your team”Generate an invitation link from /org/invitations:
POST /api/orgs/:orgId/invitationsShare the returned URL with a teammate — when they visit it and sign in, they join your organization as a member. New members start with no vendor access until you grant it (see Connect more vendors and set access below).
Skip the links entirely with a claimed domain. From /org/domains, verify your organization’s email domain and anyone who signs up with a matching address can request to join instead of needing an invite link. Verification is a DNS TXT record — add _conduit-verify.<your-domain> with the value shown on the page, then click Verify.
Promote a member to admin (can manage members, vendors, and access grants) or billing (manages the subscription, no elevated tool access) from /org/members — role changes are owner-only; admins cannot change anyone’s role. See Permissions for the full role model.
Connect more vendors and set access
Section titled “Connect more vendors and set access”Getting started connects one vendor to prove the setup works. From the Connections page (/org/catalog), connect the rest of your stack the same way — API-key vendors show a credential form, OAuth vendors redirect for consent. See Vendor connections for scopes, rotation, and OAuth specifics.
Every connected vendor has an Access editor on its connection card, where you set who can use it and at what level (Read / Write / Delete / Admin), for the whole org or per member/team. New members have no access until you grant it here — see Managing access for the full model.
Where things live day-to-day
Section titled “Where things live day-to-day”| Surface | What it’s for |
|---|---|
Members (/org/members) |
Your team — invite, change role, remove. |
Connections (/org/catalog) |
Vendor integrations, connection status, and each connection’s Access editor. |
Audit Log (/org/audit) |
Every tool call and administrative action, with the user and vendor recorded. |
| Monitoring | Usage dashboard, vendor health, and the audit log — see Monitoring your tenant for what each answers. |
Billing (/org/billing) |
Your subscription — see Billing & Plans. |
Go-live checklist
Section titled “Go-live checklist”- Team members invited (or claimed-domain auto-join configured) and accepted
- Vendor access configured per connection (Access editor at
/org/catalog) — defaults and any per-member exceptions - Every vendor your team needs is connected, not just the first one from Getting Started
- Audit log verified — make a test tool call and check
/org/audit - Billing portal access confirmed at
/org/billing
- Managing access — the full Read/Write/Delete/Admin access model.
- Vendor connections — connection scopes, rotation, and OAuth specifics.
- Monitoring your tenant — the usage dashboard, vendor health, and audit log.
- MSP onboarding — if you're reselling Conduit to your own customers instead.