Getting Started

Start with structure. Add a workspace to your internal team, some folders, some pages and share it with the people who require it. When that is already there, you can add a client portal, a database, or an automation. The getting started guides deal with the dashboard, page structure and search respectively.

They are four ways of using AI here. The editor with GenAI assists you with writing and editing the text on a page. A helper responds to questions on your material. A role is assigned to an agent, instructions and tools in order that the agent performs a task. A small application that you create to do the job you do over and over again is called an AI App.

They determine what a person is allowed to see and do. Managers run a workspace or portal, members manage day to day work, guests have restricted access to certain pages, and the external people who you invite in a portal are clients. You invite someone and select the role when you invite and may change it later.

Yes. Your records are stored in a dashboard table and you can add your own columns with the fields that you really monitor, like stage, owner or renewal date. There you can filter, sort and group. The fact that the records are stored next to your pages means that it can be placed next to the work that you provide to each client.

No. Start with the work you are already doing, like a weekly summary or status report you send a client, and get AI to do that job first. Get what it makes, before any one. What AI can work on, what it requires your consent and where your team must intervene, you determine, and you can expand on that later.

It is able to contain that work in the form of organized records as opposed to loose files which is what makes it filterable, linkable and safe to display a client in part. The choice to move everything or not is a decision you can make step by step.

By the same permission system that regulates people, you do. Delegating any of the client facing work is the reason as to why an agent works within scoped access as opposed to being above it.

You can, and you can also do it with FuseBase. We assist in defining where technology will really help, select a practical starting point and set up a process that your team can execute and manage. Some setup, custom development and training are not automatic in all plans but based on an agreed scope.

Placing the work in a location where it can be constructed on: organized records, explicit permissions and a client facing surface already linked. Tools evolve rapidly, but a piece of work that exists in a linked process is what a future tool can inherit.