Real connectors The crew shows up where the records already are.
Connections
Your stack stays. The busywork goes.
Cruma is not another place your records live. Connect a tool and the crew gets real hands inside it: scoped to what you allow, split by permission, revocable in one move.
Gmail keeps the thread. QuickBooks keeps the books. Drive keeps the document. Each connection splits three ways:
Gmail Read + draftRead email, draft replies. Asks firstSending.
QuickBooks Read + draftRead invoices, prepare drafts. Asks firstCreating or changing anything. Money never moves on its own.
Calendar Read + draftRead availability. Asks firstCreating external events.
Read, draft, and act come apart. A connection is never all-or-nothing, and the ask-first list is yours to set.
How connections workOne invoice, two kinds of record.
What connecting sharesThe original stays in the system that owns it; what Cruma adds is the work built on top, and the thread between the two.
The original
Invoice #1048
Source: QuickBooks. The original, where it lives.
What Cruma made
Deposit reminder, draft
Built from Invoice #1048, the client thread, and your payment policy.
The original, and what Cruma builds on it Point at the original. Build on it. Never hoard it.
Payoff before settingsA connection is suggested only with a reason, and the payoff shows the moment you connect: what the crew learned from it.
Keep-out means keep outFence off a folder, a thread, a client, or an account and the rule stands on every future run, visible in your Playbook.
Disconnect without dramaIf a tool is not earning its place, cut it. The crew keeps working with what it still has.
The layer between your tools was you.
Someone has to carry work from the inbox to the books to the follow-up. Hand that job to a crew that asks first.
Request an invite Access opens in waves; request yours.