Client portal for Karbon: how the build works
A client portal for Karbon that keeps client requests and uploads in one place, with staff review before any change reaches a live record.
Updated 2026-03-17
Client portal with Karbon
A client portal and Karbon meet at the point where outside clients enter the work. Your team keeps internal jobs and reviews inside Karbon, while the portal gives each client a private area to see which items are still open and which have arrived. Linking the two lets the portal draw on details already stored against a client, so a new applicant or account does not need to be typed in twice. Whether that link is practical depends on what your Karbon plan allows and which records the connected user can see, so those checks come first. Any change that flows back into Karbon should appear in the activity history, where staff can review it. For bookkeeping, financial planning and broking firms, the arrangement keeps client-facing requests separate from the internal queue.
How it works
Map the client records, tasks and document folders in Karbon that the portal needs to reference, and agree which fields are shared.
Set up a connected user in Karbon with permissions limited to the required records, so the portal shows each client exactly what they need from their own file.
Build the client login and document area as a separate service, so each client sees only their own files and open requests.
Write a sync step that creates or updates request tasks in Karbon when a client marks an item as sent, and check that each change appears in the activity history.
Add AI support for sorting uploads and drafting status summaries, with a staff member approving each item before it reaches the client or changes a task.
Test with a small set of clients and compare the activity history with what the portal shows before widening access.
Frequently asked questions
- Do I need a developer to connect a client portal to Karbon?
- Usually, yes. Connecting a portal to Karbon means reading and writing records through whatever access Karbon makes available to your account, and that work needs someone who can build and maintain a small service. Whether an integration is possible depends on your plan and on the API documentation published on Karbon's own site, which should be checked first. Once access is confirmed, MILabs can help your team define the scope of the work.
- How does a client portal stay in step with Karbon?
- The two systems stay aligned through a defined sync step. When a client uploads a file or marks a request as sent, that change is passed to Karbon as a task or document update. Changes made in Karbon can update the status the client sees in the portal. Each change should appear in the activity history so staff can review what happened and when. Check how that history records outside changes before you rely on it for review.
- How do I know a client portal works with Karbon?
- Confirm it with a test run before any live client sees the portal. Choose a small set of records, submit a request through the portal, and check that the matching Karbon task or document appears with the right details. Then compare the activity history with what the portal shows. If the two agree across several cases, the link is behaving as intended. Repeat the same check after any change to permissions or fields.
- Can I start with a part of a client portal on Karbon?
- Yes. Many teams begin with the request list and status view, which covers the most common need: clients knowing what is still open. Document upload and staff review can follow once the link to Karbon is confirmed. Starting small also shows which Karbon records the connected user can see before more data moves between the two systems. Later features, such as reminders or drafted summaries, can be added once the core flow is steady.
- How does MILabs test a client portal against Karbon?
- MILabs tests the portal in stages. The team first checks the permissions of the connected user, then runs sample requests and uploads through a small group of test clients. Each result is compared with the matching Karbon record and the activity history. Any mismatch is fixed before access widens. Only after those checks pass does the portal open to the full client list, with staff reviewing results at each stage.
Related
read these nextUp a level
More with Karbon
- Client onboarding automation with Karbon
- Email triage automation for Karbon client work teams
- Project tracker for Karbon: an internal tool for live client work
- Staff utilisation report with Karbon data
- AI adoption for Karbon: training your team on the tools you own
- AI strategy for Karbon firms
- Product idea for Karbon: shaping a tool around your client work
- Workflow automation for Karbon client work
