Connections

Connections is where you link Bitment to the outside services your firm already runs on: Google or Microsoft mail and calendar, Slack, Signal and Telegram, Asana, Quo, Fireflies, CCH Axcess, QuickBooks Online, and the credentials that power AI. Each connection page manages the link to that service. The data it brings in lives in the app that owns it, not here.

That split matters when you're looking for something you know you connected: manage the connection in Settings, but use the data in Emails, Calendar, Messages, Projects, Phone, Meetings, Taxes, or Bookkeeping.

Where to find it

Settings, the gear tile at the tail of the dock, under the Connections group in the left-hand list.

Key concepts

• Personal connection: owned by you alone. Nobody else at your firm sees it or benefits from it.
• Firm-owned connection: shared with your team. Every active member of that firm can use the data it brings in, and in some cases connect to it in Asana- or Fireflies-style setups where one teammate does the work once for everyone.
• Which kind a connection is depends on the service: some are always personal, some are always firm-scoped, and a few let you choose.

What connects where

Connect a service

1. Open the service's page under Settings › Connections.
2. Follow that page's connect flow. Most services walk you through the provider's own sign-in or consent screen and bring you back to Bitment once you're done; a few ask you to paste an API key instead.
3. Once connected, the service's data starts appearing in the app that owns it. A first connection often backfills history, which can take anywhere from seconds to days depending on the service and how much history there is to bring in.

Each service's own page in this section covers exactly what it asks for and what shows up where.

Personal vs. firm-owned, by service

• Google and Microsoft are per-mailbox, per-calendar grants, connected individually by whoever owns that mailbox.
• Slack, Signal, Telegram, and Quo are personal to the connecting individual. Each teammate who wants their own workspace, device, or phone line bridged in connects it themselves.
• Fireflies and Asana can be personal or associated with one or more of your firms. One teammate connecting a firm-associated integration is enough for the whole team; everyone else sees a read-only team connection card rather than pasting their own credential.
• CCH Axcess supports one connection per owner, meaning one for your personal use and one per firm you belong to, since each is a distinct subscription.
• QuickBooks Online supports many connections per owner, one per QuickBooks company, since an accounting firm's clients each live in their own company file.

Disconnect a service

Every connection page carries a Disconnect (or similarly named) action. Disconnecting stops syncing going forward; what it does to data already imported varies by service; each page below says what to expect. In general, disconnecting a mail, calendar, or Fireflies-style connection removes the data it brought in, while disconnecting a mirrored bookkeeping connection like QuickBooks keeps every account and entry as ordinary local data and only stops the sync.

If a connection stops working

A connection that's lost its authorization shows a reconnect prompt right on its page. Re-authorize there and syncing resumes. Bitment also notices when a service quietly stops sending updates and prompts you to reconnect, rather than silently going stale.

AI providers aren't set up here

The credentials that pay for AI, Anthropic, AWS Bedrock, OpenRouter, and Ollama, are administered by the Bitment team, not configured by you on this page. What you control is which model you use and what it costs. See AI providers and Tokens and billing.

Related

• Settings
• Google
• Microsoft
• AI providers
• Emails