DB-Leads writes into your CRM, sends messages and consumes AI budget. That is why its permissions are cut finer than "may enter" and "may not enter".
The permissions at a glance
| Aktion | Tenant-Owner | Tenant-Admin | Makler:in |
|---|---|---|---|
Open See the tool and its views. tools.use.db-leads | |||
Read contacts View contacts and the board. db-leads.read | |||
Create contacts Record single contacts by hand. db-leads.create | |||
Edit contacts Edit, change phase, notes, property leads, run-through. db-leads.update | |||
Assign Assign contacts to a person. db-leads.assign | |||
Qualify Start AI analysis, resolve findings, disqualify. db-leads.qualify | |||
Delete contacts Archive and permanently delete. db-leads.delete | |||
Start sync Trigger the sync with the CRM. db-leads.sync | |||
Start scan Run a full scan. Consumes AI budget. db-leads.scan | |||
Export contacts Download the filtered database as a file, with names, contact details and scoring. db-leads.export | |||
Share other people's contacts Additionally show one person the contacts of a colleague. db-leads.scope.manage | |||
Configure Change scan, phases, qualification, billing, sync. tools.configure.db-leads | |||
Own contacts only Restriction: only contacts you are assigned to. db-leads.read.assigned_only | |||
Reset Discard assessments, findings and pipeline state. tools.danger.db-leads |
Everything is granted in the workspace permission matrix under Settings · Team. The owner always holds every permission, regardless of the matrix.
The two nobody has by default
Exporting contacts
Export contacts is a separate permission and does not hang off reading. Being allowed to look at the list does not mean being allowed to take it away as a file.
The reason is the content: what leaves are names, phone numbers, email addresses and the AI assessment alongside them, which is the complete appraisal of a person your office looks after. Once that file sits on a private machine you cannot pull it back, cannot delete it, and when a subject access request arrives you can no longer say where it ended up.
That is why the permission is off by default for members, and why the system asks before you turn it on. What that confirmation means is described under roles and permissions and in the terms of use.
Sharing other people's contacts
The counterpart to the Own contacts only limit: instead of lifting it entirely, you release individual assignments on top of it. How that works, and what a share is not, is described under shares.
The permission deliberately does not sit with everyone who may configure the tool. Whoever maintains the field mapping should not thereby be able to move around who sees whose customer data.
Permissions in the frontend and the backend
If a permission is missing, the corresponding button disappears. That is convenience, not security: every action is additionally checked on the server. A crafted call without permission is rejected regardless of what the browser shows.
What the tool records
Every consequential action lands in the workspace audit log: who did what and when, without the contents themselves. That covers scans, syncs, disqualifications, write-back to onOffice, property leads and resets.