Overview
The Unobits platform
The shared layer every module stands on: organizations, workspace configuration, connected records, people, access, credits, notifications, search and activity.
On this page
Every module in Unobits sits on the same foundation. This section explains that foundation — the parts you meet no matter which modules you use.
What the platform provides#
| Concept | What it means in practice |
|---|---|
| Organizations and workspaces | Your business is one organization. Everything — records, people, settings — belongs to it. |
| Workspace configuration | The workspace reads in your business's own words, with the fields and stages your trade uses, on top of one shared engine. |
| Connected records | Records link across modules, so each screen can show the context that matters. |
| Members, contacts and portal users | Your team, the people you do business with, and outsiders you let in are three different kinds of people. |
| How access works | Plan, role, permissions and record visibility decide what each person can open and do. |
| Roles and permissions | Owner, Admin, Manager, Member; presets; owner-sensitive permissions. |
| System credits | One monthly pool pays for metered work such as AI, outbound sending and calls. |
| Notifications | One notifier for every module, with quiet hours and presence. |
| Search | One search across every module you can open. |
| Your personal settings | Profile, appearance, language, notifications and presence. |
The idea underneath#
Unobits separates what the engine knows from what your business calls it:
- The engine has a fixed set of objects — contacts, companies, opportunities, projects, tasks, items, invoices and so on — with fixed addresses, permission names and events. These never change between organizations, which is what makes links, automations, integrations and support work the same everywhere.
- Your workspace profile layers your business's meaning on top: a contact becomes a Guest or a Patient, an item becomes a Room or a Property, a project becomes a Case or a Job.
When a page in these docs says “contact”, your workspace may say something else. The behaviour is the same.