Frequently asked questions
Can I use FuseBase on my own, without a team?
Yes. A personal account gives you the workspace, pages, tasks and files for your own work, and there is a getting started guide written for exactly that situation. It is a normal starting point for a consultant, a freelancer or anyone running things alone. You can bring other people in later without starting over.
Can I invite someone into a personal account?
Yes, personal accounts support inviting members, and there is a guide covering how. It helps when you take on a contractor, an assistant or a first hire and want them working in the same place as you instead of over email attachments. What each person can open and edit depends on the role and permissions you give them.
How is a personal account different from a team account?
A personal account is built around one person's work. Team and business accounts add organization level capabilities such as member groups, broader roles and permissions, branding and white labeling. Which of these you get depends on your plan, so check what your subscription includes before you build a process around a specific feature.
I work alone but I have clients. Is a personal account enough?
Plenty of solo professionals start with a personal account for their own notes and tasks, then add a client facing space when they want clients to follow progress, send files or approve work in one place. Client portals and white labeling sit among the organization level capabilities, so confirm what your plan covers first.
Is AI worth it when it is just me?
Often more so, because there is nobody else to hand work to. An assistant can draft, summarize a long document or take a repetitive chore off your list while you review the result. FuseBase Work goes further, letting you set up an AI coworker with a defined role and instructions that you configure and control.
How is this different from pasting work into a chatbot?
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.
How do we prepare for tools that do not exist yet?
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.
Do we have to set this up ourselves?
You can, and you can also work with FuseBase to do it. We help identify where technology will actually help, choose a useful starting point and configure a process your team can run and control. Setup, custom development and training follow an agreed scope rather than being automatic in every plan.
Who decides what an agent is allowed to touch?
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.