Par CondoAide Team

Why a Syndicate Registry Isn't a Google Drive Folder

A condominium registry is a legal instrument with retention obligations, access rights, and evidentiary weight. Here's what CondoAide Registry V2 does that a shared folder can't: SHA-256 fingerprints, soft delete, per-category legal retention, immutable journal, verifiable export.

Cover Image for Why a Syndicate Registry Isn't a Google Drive Folder

We get this question on every demo. "We already have a shared Google Drive, why would we need a separate registry?" It's a fair question, and the short answer is: because your Google Drive doesn't know it's a syndicate registry, and your syndicate has legal obligations Drive was never designed to respect.

This week we shipped version 2 of the CondoAide registry. We took the complete list of things that separate a real condominium registry from a shared file folder, and we built each one. Here's what it changes.

1. Access levels aren't a compromise

On Google Drive, you have three options for any file: public, private, or shared with named people. For a syndicate with 40 co-owners, that means one of three things:

  • You share everything with everyone, and the board has no private workspace.
  • You keep everything private to the board, and co-owners have to email a request every time they want to see a document — which violates their access rights under CCQ article 1070.1.
  • You manually manage a permission list, document by document, with 40 email addresses. In practice, nobody does this.

In CondoAide, roles exist at the data model level, not at the file level. A board member sees everything the board sees. A co-owner sees the documents the board has made visible to the syndicate — automatically, with no need to name each user. Meeting minutes, declaration of co-ownership, financial statements: visible to all by default. Contracts under negotiation, legal opinions, internal discussions: board-only.

When a new co-owner signs up, they immediately see the documents they're entitled to. When a board member leaves, they lose access to private documents. No manual management, no list to maintain.

2. SHA-256 fingerprint on every document

This is the feature nobody thinks they need, until the day they do.

Every file uploaded to the CondoAide registry gets a SHA-256 fingerprint computed at upload time. That's a 64-character string that uniquely identifies the file's content. A single byte modified — even an added space — produces a completely different fingerprint.

Why it matters in real life:

Silent corruption detection. Files get corrupted. Not often, but it happens — a failing disk, a botched migration, an interrupted transfer. On Google Drive, you'll never know that a critical PDF lost a page, until the day you try to open it in front of the Régie du logement. In CondoAide, a "Verify integrity" button tells you in two seconds. A weekly cron job automatically checks all permanent-retention documents and alerts the board if anything is off.

Proof of non-tampering. If a co-owner contests the content of a meeting minutes two years after it was adopted, the SHA-256 fingerprint proves the document hasn't been modified since it was archived. No consumer file storage tool gives you that.

Chain of proof with signatures. When a document is electronically signed through CondoAide, the signed PDF's fingerprint becomes the official integrity anchor. The registry and the signing module share the same fingerprint, and a public page at condoaide.ca/verifier lets anyone — a notary, a prospective buyer, a lawyer — verify a signed document's authenticity without needing an account. We covered this module in detail in our post on electronic signatures and public verification.

3. Deleted documents don't disappear

On Google Drive, when someone hits "Delete," the file sits in the trash for 30 days, then it's gone. If that was the 2019 AGM minutes, you've got a problem — because CCQ article 1070 requires you to preserve meeting minutes permanently, and Bill 16 makes that obligation non-negotiable.

In CondoAide, there's no permanent deletion. For anyone. Ever.

What we built instead:

Soft delete. A board member can "delete" a document to remove it from the default view, but the file, its metadata, and all its history are preserved. A "Deleted documents" tab visible to the board shows them, with who deleted, when, and crucially why — the deletion reason is a mandatory field (minimum 10 characters). Any board member can restore a deleted document in one click.

Permanent protection for sensitive documents. Some documents simply cannot be deleted, even as a soft delete. Declaration of co-ownership, assembly and board meeting minutes, written resolutions, contingency fund studies, maintenance log, building plans: all marked permanent and protected by a database trigger that refuses the operation, regardless of who requested it. A small lock icon appears next to these documents in the UI, with the text "Permanent retention — art. 1070 C.c.Q."

Retention period respected. For documents with a legal retention period (professional invoices: 6 years, tax documents: 7 years, service contracts: 6 years), the app knows the expiry date. Before expiry, a warning appears if anyone tries to delete: "This document is under a 6-year retention period until 2031-04-15. Are you sure?" After expiry, a "Retention expired — may be archived" badge becomes visible, but the app never auto-deletes. A human always has to decide.

The disgruntled-director scenario. It happens that a director loses an election, resigns over a dispute, and tries to erase their trail before leaving. On Google Drive, they can empty a folder in 30 seconds. In CondoAide, they simply can't: critical documents are protected at the database level, and the rest leave a complete trail with their name, timestamp, and the reason they provided. This is exactly the kind of protection that justifies a dedicated tool over a shared folder.

4. Automatic sharing with co-owners

A co-owner has the right, under CCQ article 1070.1, to consult the syndicate registry. In practice, in most syndicates, this plays out as: the co-owner emails, the board member who gets the email hunts for the document, scans it if it's on paper, sends it as an attachment. If the board member is on vacation, the co-owner waits.

In CondoAide, every co-owner has an account linked to their unit. As soon as a document is uploaded to the registry and marked visible to the syndicate, it's immediately accessible in the co-owner portal — no email to send, no waiting. The co-owner logs in, downloads their minutes, checks the annual financial statement, consults the maintenance log before selling their unit. Exactly what the law prescribes, with no administrative friction.

The board retains control of what's visible. A document set to "board only" stays invisible to co-owners until a board member changes its access level — at which point the change itself is recorded in the journal.

5. A full, immutable activity log

Every action on the registry is recorded in an append-only journal: document added, downloaded, updated, deleted, restored, category changed, integrity verified, exported. Even the system administrator doesn't have permission to modify or erase a log entry — a database trigger rejects any such attempt.

The "Registry journal" page lists these events with filters (by event type, period, actor, document):

April 16, 2026, 2:32 PM — Jean Dupont deleted "Plumbing invoice 2024.pdf". Reason: "Duplicate — same invoice already filed under Contracts" Category: Contracts | Retention: 6 years

Co-owners see their own actions (their views, their downloads) but not those of others. The board sees everything. If a co-owner exercises their 1070.1 access right and asks who viewed a particular document, the answer exists.

6. One-click complete export

Sell your building. Change management companies. Leave CondoAide. Whatever the reason, you have to be able to retrieve your entire registry in a format someone else can open, without us.

The "Export complete registry" button produces a ZIP file organized by legal category, with:

  • A browsable index.html (clickable table of contents)
  • A machine-readable index.csv (for import into another system)
  • A metadata.json with syndicate info and export date
  • All documents, organized into subfolders by category (01_declaration_copropriete/, 02_reglements/, 03_pv_assemblees/, etc.)
  • The complete activity log in CSV
  • A SHA-256 manifest — a list of every fingerprint, so the recipient can verify no file has been altered after export

This is the piece no consumer storage service provides: an export that verifies itself.

In short: what a registry does that a folder doesn't

FeatureGoogle Drive / DropboxCondoAide Registry V2
Access levelsPer-file, manual, 40 emails to manageBy role, automatic, built into the data model
Integrity verificationNoneSHA-256 on every file, manual + weekly automated checks
DeletionPermanent after 30 daysSoft, restorable, reason required, permanent documents DB-protected
Legal retentionNot applicablePre-mapped CCQ categories, computed expiry dates, contextual warnings
Activity logNone (or limited on enterprise tiers)Complete, immutable, filterable, full access for board, partial for co-owners
Co-owner sharingManual, by emailAutomatic via portal, at upload time
Verified exportZIP with no manifestZIP organized by legal category + SHA-256 manifest
Legal basisNoneCCQ arts. 1070 and 1070.1, Bill 16

None of this means Drive or Dropbox aren't useful — they are, for plenty of things. But a condominium registry isn't a file folder. It's a legal instrument, with retention obligations, access rights named in the statute, and evidentiary weight that needs to hold up over twenty years. Those constraints aren't satisfied by generic storage.

What's coming next

Registry V2 is live today for all CondoAide accounts. Existing syndicates are migrated automatically — no action required on your end. Current documents get their default retention category, and the SHA-256 fingerprint is computed retroactively on the full history.

Up next: the meeting minutes module that plugs directly into the registry with built-in signatures and public verification, then an extension of the activity log to automatically document co-owner 1070.1 access requests.

Log in to your syndicate, go to the Registry tab, and check out the new "Registry journal." You'll see the full document history since you started using CondoAide. That's the difference between running a syndicate blind and having an actual logbook.

Not on CondoAide yet? Our free registry checker tells you in two minutes whether your current registry meets the requirements of CCQ article 1070 and Bill 16. No account needed, no documents to upload — just answer about ten questions on what you keep today.