FuseBase Basics

Content is in a plain hierarchy. The workspace contains folders, the folders contain subfolders and pages and the pages contain the blocks you write in. One of the structures that tags cut through so related stuff can be located in one place no matter where they live and favorites make the few you open each day one click away.

Blocks are used to create a page and a block is a single piece of content: a paragraph, a table, a file uploader, a dropdown list, a progress bar. You move blocks about to rearrange them, stack them in columns and resize. That is why a single page could be a document and a tiny working tool simultaneously.

Tasks you make on any page are also visible in the task dashboard, so you only have a single list rather than searching through folders. When you would like to see the work as a flow, a task board displays the same work in columns by status. It is narrowed down by filters to a single person, date range or project.

Tags are labels you make on pages and items to allow related things to be found together even though they might be in different folders. They fit something a folder cannot say, like a stage, a client name or a quarter. Both search and filters read tags, therefore, a short consistent set is better than a long set.

Search and AI can help to find things more easily, yet structure remains important, since clear names and organized folders tell an assistant or an agent where to go and what it can use. Always organize people first. The actual transformation is that less of your time is spent on filling and that more is spent on what to keep.

The kitchen is where your crew is to work and the dining room is what the guest looks at. They are various experiences with various permissions, yet they are a part of a single operation. FuseBase provides you with neither a portal that is glued to another workspace, but rather one that is connected to the workspace.

No. FuseBase is able to grow what already exists instead of requiring a migration to proceed. The most popular is to introduce a client facing layer to an existing internal configuration and attach the two, only to start moving more when it is profitable.

The portal is no longer a filing cabinet but a place where work occurs in-between visits. The handy question is no longer what a tool can do but what you are prepared to delegate in the process and what you would still prefer to commit yourself to.

It supports a custom domain, meaning that the portal is located at an address owned by your business. Availability is based on your plan, so check it before your account before you guarantee it to a client.