# Connecting Twilio, EasyPost and TaxJar with your own account

> Each company connects its own accounts. Keys are checked with the provider first, stored encrypted, and never shown again. Only company administrators can connect or disconnect.

Section: Settings and administration · Canonical: https://intubu.intuitivecapital-dai.com/docs/connect-integrations

Integrations, then the provider's card.

**Your accounts, not ours.** Every company uses its own accounts with these services: your own mailbox for email ([Connecting your email](https://intubu.intuitivecapital-dai.com/docs/connect-mailbox)), your own Twilio account for texts, your own EasyPost account for postage, your own TaxJar account for sales tax filing, your own Stripe account for card payments ([Card and ACH checkout on invoices](https://intubu.intuitivecapital-dai.com/docs/online-payments)). What they charge, they charge to you directly; the messages, labels and filings are in your name.

**Which are connected here.** Three providers are connected on the Integrations page with a key:
- **Twilio** — *Account SID*, *Auth token*, and the *Sending number or Messaging Service SID*. See [Text messages (SMS) through your own Twilio account](https://intubu.intuitivecapital-dai.com/docs/text-messages).
- **EasyPost** — an *API key*. A test key (EZTK…) buys sample labels at no charge; a production key (EZAK…) buys real postage. See [Buying shipping labels at the pack station (EasyPost)](https://intubu.intuitivecapital-dai.com/docs/shipping-labels).
- **TaxJar** — an *API token*, with *Sandbox token* ticked only for a sandbox token. See [E-filing sales tax with TaxJar (E-file)](https://intubu.intuitivecapital-dai.com/docs/sales-tax-efile).

Other cards say where they are connected instead: email under Email & Calendar → Connect accounts, bank feeds under Banking, card payments under Settings → Payments. Items marked as on the roadmap cannot be connected yet.

**What happens when you press Check and connect.** The key is checked with the provider first. If the provider refuses it, nothing is stored and the message says why. If it is accepted, it is stored encrypted and is **never shown again** — not to you, not in an export, not to support. The card then shows *Connected*, the account, and since when.

**Replace keys** swaps in a new key the same way. **Disconnect** deletes the stored key; reconnecting means entering it again. If a provider later stops accepting a stored key, the card shows the error in red and asks you to reconnect.

**Who can.** Only a company administrator can connect or disconnect. Everyone else sees which providers are connected.