Every vendor, document and record belongs to one workspace, and the database itself refuses to show it to anyone else.
Separation isn't a filter added by each screen. The database checks workspace membership on every read and write.
Certificates, W-9s and lien waivers sit in private storage, filed under your workspace.
Vendors and brokers never get a login. Each link does one job for one request.
The sample workspace you explore in Demo is built into the app, never stored with real records.
| Typical tools | myCertGate | |
|---|---|---|
| Where separation is enforced | In each screen's code | In the database, on every request |
| If a screen has a bug | Other customers' data can show | The database still refuses the rows |
| Vendor access | Shared logins or emailed files | Revocable, one-job links |
| Files | Shared folders or public links | Private, workspace-scoped storage |
Separation also applies inside your team. Five roles decide who can approve documents, override payment holds, invite people or only view. Every approval and override is recorded with who did it.
Staff pages require two-step verification. Support viewing is read-only, ends after 30 minutes and is written to an audit log that can't be edited.
No. Every record is tied to one workspace, and the database only returns rows to members of that workspace. A screen bug can't change that rule.
You send a single-purpose upload link. It only accepts files for that one vendor request, can be revoked, and stops accepting uploads once the vendor submits.
No. Demo sample data is built into the app itself. Exploring Demo never reads, writes or mixes with your live records.
Only with two-step verification, and every view is logged. Support viewing is read-only and ends automatically after 30 minutes.