Find your way around FuseBase

It is the product documentation for FuseBase, currently 274 articles across 19 categories. It covers pages and tasks, client portals, databases and dashboards, AI assistants and agents, automation, branding, mobile apps, imports and account settings. Each category page lists its guides so you can browse a topic instead of searching blind.

Begin with Getting Started, which explains the structure of workspaces, portals and pages and the roles that decide who can see what. FuseBase Basics goes a level deeper into daily work such as tasks, tags and navigation. Once you know where things live, move to the category that matches the job you are trying to do.

FuseBase is an AI native client portal and client collaboration platform for businesses that serve clients, operating since 2014. It joins internal team work and the client facing experience into one process: internal workspaces, white labeled portals, records, apps, AI assistants and agents, automation and hosting.

Go to the category that owns it. Portals covers client access, branding and client notifications. Table and Database covers records, views and CSV import and export. FuseBase AI and FuseBase Work cover agents, services and integrations. When you are unsure which one owns a feature, the guide titles in each list are specific enough to scan.

Yes, and several categories exist for that. FuseBase AI covers assistants and agents, FuseBase Work covers AI coworkers given a company role with defined responsibilities and instructions, and Automations covers the rules that set them off. The pattern is the same throughout: your team is in charge and decides what AI is allowed to do.

A general chat tool has no standing role, no access to your client records and no rules about what it may act on. An AI coworker in FuseBase is set up against real work, with scoped permissions, inside the process it is helping with.

You do, through the same permission system that governs people. An agent operates inside scoped access rather than above it, which is what makes delegating any of the client facing work reasonable in the first place.

Yes. Each client can have a portal of its own, branded to you, holding only the documents, updates and approvals that client should see. Access is set per person and per item rather than per workspace.

By putting the work somewhere it can be built on: structured records, clear permissions and a client facing surface that is already connected. Tools change quickly, but work that lives in a connected process is what a future tool can pick up.