This page is generated from the product itself — the same source the built-in assistant answers from — so it cannot disagree with either.
What is CRM?
CRM — Contacts, companies, vendors and a sales pipeline. Keep contacts, companies and vendors in one place, and move deals across a pipeline board. On the App page it is listed under “Extra apps”. 6 of its screens are available today.
What screens does CRM have?
CRM ships these screens today:
- Opportunities: Pipeline · Deals · Pipeline Stages
- Relations: Contacts · Companies · Vendors
Being listed here means the screen opens today. On its own it does not mean every action on it is available — ask about the specific task, and where something is not built the answer says so rather than guessing.
Each screen opens for anyone who holds the permission in the last column. Being listed means the screen opens today; ask about the specific task if you need to know whether every action on it is available.
| Screen | Section | Permission needed |
|---|---|---|
| Pipeline | Opportunities | crm.deals.read |
| Deals | Opportunities | crm.deals.read |
| Pipeline Stages | Opportunities | crm.pipelines.read |
| Contacts | Relations | crm.parties.read |
| Companies | Relations | crm.parties.read |
| Vendors | Relations | crm.parties.read |
Messages CRM can show
Each message is quoted exactly as the product shows it. Most say what to do in the message itself; where one names a setting, the place to change it is the app’s own settings screen or Company settings.
That contact is not in this workspace.
This pipeline already has a stage called {name}. Two columns with one name cannot be told apart on the board.
The reference {code} already belongs to another contact.
A contact needs a name.
{parentName} can only be named as the organisation a person works for.
A contact cannot work for itself.
“{role}” is not one of the roles a contact can hold.
{field} needs an amount and a currency together. Neither means anything on its own.
{currency} is written with {expected} decimal places, not {given}.
That deal is not in this workspace.
That stage belongs to a different pipeline.
{title} is already marked {status}. Raise a new deal rather than re-opening this one.
That bank account is no longer on this contact.
A bank account needs an IBAN or an account number. Either one is enough.
That is not the shape of an IBAN (it ends {last4}). Check it, or put it in the account number box instead.
A label needs a name.
That label is not in this workspace any more.
A sector needs a name, in one of the languages this product speaks.
That sector is not in this workspace's list.
“{name}” is already in your sector list. Pick it instead of adding it again.
Labels, sectors and bank accounts need a database update that has not been applied to this workspace yet. Ask your administrator to run pending updates — everything else about a contact works meanwhile.
A deal needs a title.
That is longer than {max} characters. Shorten it and save again.
A deal’s stage and status are not changed by editing it. Move it to another stage, or mark it won or lost, instead.
Give the date as a calendar date — for example 2026-10-01.
The person chosen to own this deal is not an active user of this workspace.
Say what the next step is before giving it a due date.
Next steps on deals need a database update that has not been applied to this workspace yet. Ask your administrator to run pending updates — everything else about a deal works meanwhile.
This contact has no picture now.
Pictures on contacts need a database update that has not been applied to this workspace yet. Ask your administrator to run pending updates — everything else about a contact works meanwhile.
{name} ({code}) already has this e-mail address. Open that contact, or create a new one anyway.
{name} ({code}) already has this tax number. Open that contact, or create a new one anyway.
A contact cannot be merged into itself. Choose a different contact to keep.
Choose at least one contact to merge into the one you keep.
At most {max} contacts can be merged at once. Merge the rest in a second step.
{name} is a different kind of contact (a person and a company are never one contact), so it cannot be merged here.
That contact's details were erased on request, so it cannot be merged.
Merging contacts needs a database update that has not been applied to this workspace yet. Ask your administrator to run pending updates.
That merge could not be found. It may belong to another workspace.
This merge has already been undone.
The merge cannot be undone: a record it moved ({table}, {rowId}) has been changed or removed since, and undoing would overwrite that later work.
The merge cannot be undone: a field it filled on the kept contact ({field}) has been edited since.
The merge cannot be undone: the merged contact's details were erased on request, and undoing would bring them back.
The merge cannot be undone: one of the two contacts has been erased, removed or merged again since.
"{email}" is not a valid e-mail address.
"{purpose}" is not a purpose an address can have.
{email} is in the list twice.
A contact can have at most {limit} e-mail addresses.
Several e-mail addresses per contact need this company's database update. Ask your administrator to run it.
{name} is a company, not a person, so it cannot be added to a company as one of its people.
{name} is not one of this company's people.
Was this page helpful?
Thank you.
Your answer is kept on this device only. Nothing is sent anywhere — there is no service behind this button yet, and this page will say so until there is.