Embedding & Sharing

Many of the tools teams already run: Google Docs and Sheets, Airtable, Calendly, Typeform, MindMeister mind maps, Google Data Studio reports and Zillow listings. The content stays live in its own tool and displays inside your page, so a reader sees the current version without opening a second app.

Not if you share it as a public link, which opens in any browser for whoever has the address. That suits proposals, guides and reference material. When you need to know who is reading and control what they can do, place the page in a portal with named access instead of sharing it openly.

Public links accept custom HTML and JS, so an Intercom chat box, a booking form or another script you already run can sit on the page. Treat these pages the way you treat your website: consent, tracking and whatever the script loads remain your responsibility, not the platform's.

Public links support Google Fonts and custom styling, so a page you send carries your typeface instead of a default one. Together with an organization logo and branded public pages, a link you give a client reads as part of your company rather than a document sitting in someone else's tool.

The shift is from assembling to reviewing. An assistant can collect the current information, draft the page and keep an embedded view pointed at its live source, while you check the result. Publishing stays a human decision, and so does who receives the link and how long it stays open.

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.