Last updated: August 2026

Notes Vault Tree: Every Note Your Business Writes, Private by Default

Notes Vault Tree is the written-knowledge vault inside FireFlight Data Systems. Meeting notes, SOPs, safety briefings, client correspondence, job notes, checklists, plus policies live in one place with their attached files. The structure is one your team already understands: Bookcase, Shelf, Binder, Page.

Where can a business keep every note private but still findable? Notes Vault Tree stores what your team writes down, together with the files attached to it, inside FireFlight. A note is private by default. Sharing is deliberate: read-only or editable, to named people or to everyone. No second app. No separate subscription.

See it with your own notes and files. Not a canned demo.

Book a Demo Contact Sales

Why does nobody put their real notes in the shared system?

In 2026, a working team writes more down than it ever has. Meeting recaps land in chat threads. SOPs live on someone's desktop. The current safety briefing sits in an email attachment from March. The knowledge exists somewhere. Finding the current version of it is the actual problem, and that problem compounds every month the business grows.

Most note tools make it worse through their defaults. A new note is visible to the whole workspace unless you go lock it down, so people write carefully instead of honestly. Even the folder counts leak. A folder showing (12) that only opens 4 items announces that eight private notes exist. The count itself becomes the disclosure.

So the honest notes migrate somewhere else. The real client history sits in a personal drive. Candid job notes live where nobody else can read them. What remains in the shared system is a sanitized fragment of what the business actually knows, and when the person holding the rest is out, that knowledge is out with them.

How does a private-by-default notes vault actually work?

The structure is a physical metaphor nobody needs training on: Bookcase, Shelf, Binder, Page. Everyone already knows a binder sits on a shelf. You build the tree to match how your business actually thinks, by department, by client, by job, by year. Rearranging is a drag, not a rebuild. Move a note or an entire binder, navigate away, close the browser, come back tomorrow. It is exactly where you put it.

Privacy runs in the opposite direction from most systems. Instead of starting visible and asking you to restrict, every note starts as yours alone. Sharing is a deliberate act with real granularity: read-only to named people, editable to named people, or open to everyone. Until you take that step, the note does not exist for anyone else.

The edges do not leak either. Counts in the tree show only what you can open, so the existence of someone else's private work never shows through. Attachments obey the note they belong to. Share a note and its files come along. Share it read-only and the files cannot be detached. One rule, applied everywhere, with no separate permissions screen for documents drifting out of step.

What apps does Notes Vault Tree connect to?

The vault is part of FireFlight, not a bolt-on beside it. Notes live in the same tenant as the operational records they describe. Same login. Same permission model.

Projects appProjects Work Orders appWork Orders Contacts appContacts Client Tracking appClient Tracking
Private by Default Drag and Drop Moves Server-Enforced Structure

Who can open a note, plus what the server refuses

A note belongs to its author until the author deliberately shares it: read-only or editable, per named person, or open to everyone. The tree shows each viewer only what that viewer can open. Nothing leaks through the counts or the labels.

Structure rules live on the server, not in hidden buttons. A shelf cannot land inside a page. A container cannot contain itself. However someone reaches the data, the same rules answer. The vault runs on the same login plus the same permission model as the rest of your FireFlight tenant, so there is no second set of accounts to audit.

Ikhana, the FireFlight advisor
Meet Ikhana

Your Personal Guide on Every Page

From the first click to the final step, Ikhana, your on-screen tutor, shows you how it all works. Every field, every button, every page explained with clarity, just a tap away.

Learn more

What does Notes Vault Tree give your team?

  • One vault for written knowledge. Meeting notes, SOPs, safety briefings, client correspondence, job notes, checklists, plus policies, held together with the files attached to them.
  • A structure nobody needs training on. Bookcase, Shelf, Binder, Page. A binder sits on a shelf. Everyone in the building already knows that.
  • Built around how your business thinks. Arrange by department, by client, by job, or by year. The tree matches your operation instead of forcing a template on it.
  • Drag and drop that sticks. Move a note or a whole container. Navigate away, close the browser, return tomorrow. It stays where you put it.
  • Private by default. A note is yours until you deliberately share it. Read-only or editable, to named people or to everyone.
  • Counts that never leak. The tree shows only what you can open. The existence of private notes stays invisible to everyone else.
  • Attachments that obey the note. Share the note, the files come along. Share it read-only, the files cannot be detached.
  • Structure enforced on the server. A shelf cannot drop into a page. A container cannot sit inside itself. The rules hold however the data is reached.

The same team since 1995

Phoenix Consultants Group has built custom business software since 1995. That is more than 30 years and over 500 applications. The work spans fleet fueling for municipal operators, physician credentialing for multi-site staffing firms, plus airport ground equipment management. All of it stands behind the platform your notes now live in.

Notes Vault Tree is not a bolt-on from a vendor you have never met. It is one workspace in a platform PCG hosts and runs. Every call is a real phone call, answered by the people who built the software. Deployments run weeks, not months.

What changes operationally once the vault is in use?

  • Written knowledge lands in one structure instead of scattering across personal drives plus chat threads.
  • Reorganizing is a drag, not a rebuild, and the move is still there tomorrow.
  • Nothing gets exposed by accident. A note stays invisible until its owner shares it.
  • Attachments carry the note's access level automatically, with no second permissions screen to maintain.
  • Each person's tree shows only what that person can open, so private work never advertises itself.

Frequently Asked Questions

Can I keep my notes private from the rest of my team?
+
Yes. Every note is private by default. It stays yours until you deliberately share it, read-only to named people, editable to named people, or open to everyone. There is no workspace-wide visibility to switch off, because visibility was never on in the first place.
Can my coworkers tell that my private notes even exist?
+
No. Counts in the tree show only what each person can actually open. A binder you cannot see into does not advertise how much it holds, who has been writing, or when. The vault never reveals the existence of a note you were not given access to.
What happens to attached files when I share a note?
+
The files follow the note. Share a note and its attachments come with it at the same access level. Share it read-only and the recipient cannot detach the file or pull it out separately. One rule, applied everywhere. No separate document permissions screen to drift out of step.
How do we organize notes for the whole business without training anyone?
+
The structure is Bookcase, Shelf, Binder, Page. Nobody needs a course to know a binder sits on a shelf. You build the tree to match how your business thinks, by department, by client, by job, by year, then rearrange it by dragging. Moves persist: close the browser, come back tomorrow, everything is where you put it.
What kinds of notes and documents can the vault hold?
+
Anything your business writes down and needs to find again. Meeting notes, SOPs, safety briefings, client correspondence, job notes, checklists, plus policies, together with the files attached to them. If you wrote it down, it fits here.
Do we need a separate app or a second subscription for this?
+
No. The vault sits inside FireFlight with your projects, work orders, plus contacts. Same login, same permissions, same tenant. There is no exporting notes to a second system to find them later, and nothing new to buy or maintain.
How fast can a team actually start using it?
+
FireFlight deployments run weeks, not months. The vault ships inside the platform, so a live tenant has nothing extra to install and no second login to set up. The metaphor does the training: a binder sits on a shelf, plus everyone already knows it.
Allison Woolbert
Allison Woolbert
Principal, Phoenix Consultants Group

Allison Woolbert has designed and shipped custom business software since before founding Phoenix Consultants Group in 1995. Across 31 years and more than 500 applications, from fleet fueling to physician credentialing, she leads the platform work behind FireFlight Data Systems.

phxconsultants.com fireflightdata.com LinkedIn

FireFlight Data Systems is built and hosted by Phoenix Consultants Group. PCG founded 1995. Content reviewed August 2026.