Connect Karbon
One approval in the console. Work items, document requirements, and notes join the work.
Updated August 2026
One approval brings the practice-management half of a job in reach: what an engagement requires, who owns it, where the record stands. Two minutes, once, by an owner. Every system is separately approved; none requires another.
- Karbon12 people authorized · 6 read capabilities, 5 actions · last verified read 4 minutes agoConnectedWithdraw
- Microsoft 36512 people authorized · 7 read capabilities, 4 actions · last verified read 2 minutes agoConnectedWithdraw
- Salesforce5 people authorized · 3 read capabilities, 2 actions · last verified read 1 hour agoConnectedActions pausedWithdraw
Approve Karbon once
In the console, under connected systems, start the Karbon connection. It asks for the two credentials Karbon issues under Settings, then Connected Apps, then API Applications. Paste them once; they are held inside the firm's environment and never shown again.
What that approval carries, and how to end it
| Each connection | On its own terms |
|---|---|
| Holds | Its own credentials, inside the firm's environment. The console never displays them |
| Exposes | One closed set of registered reads and typed writes, at one capability revision |
| Is bounded by | A budget for how much any single piece of work may query it |
| Ends at | Withdraw, on the same row. Work that already completed keeps its record |
A versioned normalizer turns Karbon's records into the neutral facts a piece of work asks for, so requirement, evidence, scope and status meaning belongs to the firm rather than to one vendor's field names. Several connections to the same provider can coexist, and no firm-wide switch stands in for one.
What it reads and writes
| Karbon | What it brings |
|---|---|
| Reads | Work items and assignments, document requirements and Integration Tasks, notes, work status, contacts where supported, file metadata, source links with the provider's revision |
| Writes | Requirements, Integration Tasks, work status, notes, next chase date |
Approving Karbon is not permission to read Karbon. Authority is assigned per approved kind of work, and rechecked every time (how Proxara works).
The chase this anchors
Requirements get reconciled against what actually arrived in mail and in files, so an item marked missing that came in by email is separated from one genuinely absent. The update lands on the Karbon work item and is read back to confirm.
You're connected
The Karbon row reads Connected. Ask what is still missing for an engagement.
If something doesn't work
- Row says sign-in needed? Reconnect there; nothing else is affected.
- No Karbon in the answer? An unreachable system returns an honest partial result naming the missing source.
- Reads work but updates do not? Reads and typed writes are separate authorities.
Where to go next
| To do | Read |
|---|---|
| Add mail and files | Connect Microsoft 365 |
| First requests | What to ask for |