🤖
Bob may do no more than you
Bob and every external agent via MCP see and change only what the signed-in user may. No data leak through AI, no detour via automation.
Permissions
Every role sees exactly what belongs to it.
The site manager sees everything, accounting only numbers, the subcontractor only their tasks, the intern their view — and the client's inspector exactly the entries you share with them. Not coarsely per app, but per status and per field. The matrix shows it at a glance; Bob complies.
- Roles per app, teams org-wide
- Matrix per status × field
- View · edit · create · delete
- Guests without a user licence
- Audit log
Roles & teams
One role per job, one team per crew.
Roles belong to the app: admins, site management, installation, accounting, customer. Teams belong to the organisation and carry roles into many apps — a new fitter joins team "Installation South" and immediately has the right view in every app. Whoever holds a role via a team counts exactly like a direct member.
- ✓Default roles on every app, your own in addition
- ✓Teams carry roles into many apps
- ✓The owner of an entry can be a role
- ✓Sales and catalogue with their own role matrix
Guests & externals
Invite the customer without buying them a licence.
An entry can be shared with a person outside the organisation — the inspector sees the report, comments, uploads a photo, and nothing else. No account subscription for guests, you pay once per shared entry. Public forms take reports from people who do not even have a login.
📜
Audit log
Who changed what when — per field, with version. Roles, releases, deletions and exports are recorded as events.
🇩🇪
One organisation, one schema
Every organisation lives in its own database schema in Germany. No path from one customer to another — technically, not just by rule.
Ready to free your processes from tool chaos?
No-obligation introductory call. We build a live app with you that mirrors your real workflow.