Using Your App
How everything connects
Every piece of information is a record, records link across every module, and relationships are always visible from both sides — so you never have to guess what belongs to what.
Most software makes you keep the map in your head: the file is in one place, the meeting in another, the customer in a third, and remembering that they belong together is your job. This application works the other way. Underneath everything — contacts, jobs, meetings, files, conversations, tasks, whatever your organization tracks — is one connecting layer, and every item on it can be linked to any other. Once things are linked, the connection travels with both of them, everywhere, forever.
One example, followed all the way through
Say there's a site-visit meeting on the calendar. Attached to it: a floor plan file and the customer it's for.
- Open the meeting — you see the floor plan and the customer right there.
- Later, you find the floor plan through search instead. Opening it shows you it belongs to that site visit and that customer — you arrived from a completely different direction, and the context came with it.
- Open the customer — the meeting and the file appear among their related items, alongside every other conversation, task, and document tied to them.
Nobody filed anything three times. One link, made once, is visible from every end of it. That's the whole trick, and it applies across every module — a task can point at an invoice, a conversation at a job, a file at all of them.
Relationships are two-way, always
This is the part worth internalizing: there is no such thing as a one-way attachment. Attaching a file to a meeting is the same act as connecting that meeting to the file. So the question “where is this used?” — the one that's unanswerable in a folder full of documents — always has an answer here. Open anything, look at its related items, and you're looking at everything it's part of.
Where you'll see it
- Related items on every record — open anything and its connections are listed: what it belongs to, and what belongs to it, across every module.
- The inbox — conversations are records too, so an email thread can be linked to the customer and job it concerns, and shows up from their side just like a file would.
- Insights and follow-ups — when the application surfaces something (an insight, a reminder), it arrives attached to the record it's about, with that record's connections one click away.
When you create something, take the two seconds to link it to what it belongs to. That one link is what makes it findable from every direction later — it's the highest-return habit in the whole application.
Connections respect permissions
Related items follow the same access rules as everything else. If a meeting is linked to a document you don't have access to, that document simply doesn't appear in your related view — and following connections outward never reaches anything you couldn't open directly. Two colleagues looking at the same record can legitimately see different related items; that's the permission model working, exactly as it does in search.
Why this beats folders
A folder can hold a file in exactly one place. A record can be connected to a meeting, a customer, a job, and an invoice at once — because those are relationships, not locations. The file isn't in the meeting; it's connected to it, and to everything else it genuinely relates to. When someone asks “what's the story on this customer?”, the answer isn't a scavenger hunt across five modules — it's one screen of related items, assembled by the system, filtered to what you're allowed to see.
Capability review: 2026-09-14. For exact current technical availability, use the generated API Map and first-class module inventory.