- Client Id
- 01a0c2f1-4d3e-7b2a-9f10-6c1e8a2b4c01
- accounts@harbourfinch.example
- Created At
- 14 Mar 2026
- Created By
- Alex Morgan
01 — Records
Open a record. It’s all there.
Status, details, files, notes and history sit on the record itself. Open one and the whole picture is in front of you. Nothing to go looking for.
Swipe through the cards. Tap one to watch it happen; tap again to stop.
- The fields you were missing. Add your own: text, number, date, link, true or false. Copy any of them in a click.
- The paperwork. PDFs, spreadsheets, documents and images. 25 MB each, ten at a time.
- What was said. Notes, signed with a name and a time.
- The fields you were missing. Add your own: text, number, date, link, true or false. Copy any of them in a click.
- The paperwork. PDFs, spreadsheets, documents and images. 25 MB each, ten at a time.
- What was said. Notes, signed with a name and a time.
User PermissionsManage user access and privileges
| Permission | Read | Create | Update | Delete |
|---|---|---|---|---|
| Clients | ||||
| Projects | ||||
| Tasks | ||||
| Invoices | ||||
| Users | ||||
| Organizations |
02 — Team
Who sees what, per person.
Read, create, update, delete. Four flags per capability, granted one at a time. Nobody gets more than the job needs.
- Nothing by default. Every permission is granted, never assumed.
- Change it when the job changes. It takes effect immediately.
Built carefully
The unglamorous parts, done properly.
Small teams do not have a security team. These are the defaults you get on day one.
- Isolation by defaultEach organization’s data is separated at the database level. Nobody sees another organization’s records.
- Audit trailInsert, update, archive, unarchive, delete and restore, recorded with who and when, across fourteen record types.
- Error monitoringFailures are caught and reported automatically, before anyone has to write in.