The apps, and how they fit together
On the left sit five apps. They are not five programs: they are five views of one database.
| What it holds | |
|---|---|
| CRM | Organisations, contacts, the deal pipeline, products |
| ERP | Projects, customers, time entries, rate cards, people |
| Processes | The steps your company repeats, and every run through them |
| Knowledge | Documents — written here, or files in a folder you chose |
| Goals | Objectives, key results, and the org chart they hang on |
Beside them, reachable from the top bar rather than the app list: Tasks — the to-do list — and the background-process list from work that runs in the background.
One company, not five copies
A customer in ERP and an organisation in CRM are the same row. Master data — companies, people — lives once, in a shared place both apps read.
That is why creating "Meyer GmbH" as a customer when it already exists as a partner does not make a second Meyer GmbH: the form matches on the name and promotes the one that is there.
It also means an answer can cross apps without an export: "Which customers have an open deal and an unbilled project?" is one question, not three.
What you see is what your role allows
Every list is filtered to what you may see, and the rule lives in the database rather than in the screen. The agent inherits exactly that — see working with the agent.
Every app is a description
A built-in app is not hand-built screens. It is a description — these tables, these views, this form — that the app renders. That is why the agent can extend them, and why an app you build yourself looks and behaves like the ones that shipped.
Opening them
Click an app to open it beside the chat. The two most recently used stay in the sidebar; the rest live behind More. The panel can sit beside the chat or above it — the two icons at the top right switch that, and full screen is a third option when a list gets wide.