Page Editor

A page is built from blocks: text, tables, files, embeds and more. You can drag a block somewhere else, place blocks side by side in columns and resize them, which is what turns a page into a layout instead of one long strip of text. The navigation guide covers moving blocks, creating columns and resizing.

Yes. Tables inside the document editor support sorting columns, filtering rows and a calculation panel for totals and other summaries at the foot of a column. That is enough for a budget, a checklist or a small tracker that belongs with the text around it. For records you reuse in several places, a database fits better.

Collapsible headings and toggles let you fold a section away until somebody needs it, so a long document opens as an outline rather than a wall of text. Code blocks with highlighting keep technical snippets clearly separate from prose. Both are small habits that make a reference page much easier to come back to.

Yes, comments can be left on an individual table cell, not only on the page as a whole. That keeps a question attached to the exact figure or row it concerns, which helps when a colleague or a client is reviewing a line in a quote, a schedule or a budget. Who can comment depends on the access you granted.

AI in the editor can draft, rewrite or continue a section without you leaving the document, and agents can be used there too. Treat the output as a first pass: read it, correct what is wrong and decide whether it is ready for anyone else. The page stays yours, and nothing reaches a client until you send it.

That is the real risk rather than the tools themselves. A team can be excellent and still lose to a competitor whose process stopped being manual. The practical answer is to move one recurring process at a time and keep people in control of the judgement.

Start with one process that repeats and already causes friction, usually something client facing that involves chasing, resending or re-explaining. FuseBase can help you pick it and put it into practice, under an agreed service scope.

Yes. Review requirements are part of how you configure delegated work, so automated or AI prepared output can wait for a named person. Autonomous and human reviewed execution are both supported, and neither is forced on you.

That is the usual case. The internal side works on its own, and the client portal is added where a client actually needs to take part. FuseBase is not limited to moving information between two spaces.