Security & access
The contents of a significant home are sensitive by nature: where the safe is, who holds a key, what the gate code is, what a system cost. Tidewater OS is designed on the assumption that this information must be narrowly held and that every access to it should be accountable.
Every record belongs to exactly one organization, and that boundary is enforced by the database's own row-level policies rather than by application code that could be bypassed. A query that reaches for another organization's property returns nothing — there is no code path that widens it.
Portfolio admin, property manager, field user and owner each see a different amount of the record. Access can be narrowed further to individual properties, so a caretaker responsible for one house does not see the rest of the portfolio.
Alarm codes, key locations, security procedures and confidential documents carry a sensitivity level. Raising the level narrows who can read the item, including inside the organization that owns it.
Files live in private storage. A file is reached through a short-lived, permission-checked link issued for one request; there is no open URL to guess, share by accident, or leave behind in a forwarded email.
Changes are recorded with the actor, the field-level difference, the timestamp and the property. Audit entries cannot be edited or deleted by anyone using the application — the database rejects the attempt.
Extraction from documents produces proposals, not records. A person reviews each one before it becomes part of the authoritative account, and document content is always treated as untrusted input rather than as instructions.
Team, owner and field users sign in through their own doors and land in the experience built for them, but they are governed by the same permissions. Nothing about a separate entrance grants separate rights.
An executive property summary can be shared with someone who has no account through a private link. The link points at a published snapshot, can carry an expiry, and can be revoked at any time.
We would rather answer them before you start. Ask in your access request and we will address them directly.