🇮🇪 REPUBLIC OF IRELAND · ESTATE AGENCY
CHAPTER 05 / 06 · THE TRUST REVELATION
The contacts in your database represent professional relationships, commercial confidence and information entrusted to your business. Those assets must not become visible to a neighbouring lettings office or mortgage brokerage simply because the same group owns them. Kadpex's intended security architecture separates professional workspaces, staff authority and customer-controlled evidence. Access must be checked on the server, not merely concealed in a menu, and the proposed controls must pass rigorous testing before any operational claims are made.
PROPERTY SALES & AGENCY INTELLIGENCE · Dedicated professional environment
A group might run sales, lettings and mortgage advice from the same address. That does not create permission for its employees to browse each other’s customer correspondence, valuations, bank records or case histories. Physical convenience is not data authority.
Kadpex’s intended professional isolation must be enforced by the server, data model and AI tooling, not simply by hiding a navigation tab. A director’s commercial ownership also cannot be treated as a blanket right to read every confidential record. Trust has to be demonstrated through rejected access attempts as well as successful authorised ones.
Kadpex is being engineered around customer-controlled evidence, profession-specific access and supervised execution—not unrestricted central access to client files.
Sensitive end-client documents remain within authorised customer-controlled systems, with scoped references used where appropriate. Permission checks must deny access from neighbouring professional environments at the API and record level.
An estate sales licence never opens letting, mortgage or other branch files by default. Sensitive identity material must not be copied to central Kadpex simply to support a report.
Signed receipts, review controls, revocation and audit history are subject to engineering and independent acceptance. Cross-boundary exceptions require explicit scope, legal basis, logging and independently verified grants.
Estate Agency, Letting Agency and Mortgage Brokers maintain independently licensed and authorised workspaces. Even if all three share a company owner, office, reception desk or CRM provider, operational access is not inherited.
For a real deployment, that must be enforced by authentication, licence checks, database/API controls, evidence permissions and agent tooling—not by simply hiding a menu item.
Sales, vendor and buyer casework require separate entitlements and scoped identities.
NO INHERITED LETTINGS OR BROKER ACCESSLandlords, tenants and property management stay within the authorised lettings environment.
NO INHERITED SALES OR BROKER ACCESSBorrower financial records, advice correspondence and lender casework require their own professional permissions.
NO INHERITED SALES OR LETTINGS ACCESSThis is an access-control architecture specification, not a claim that the current application already enforces all these boundaries.
Making a process faster is not enough. We must be able to explain where a fact came from, which action was permitted and who took responsibility.
Architecture ambition · subject to independent testing and security acceptance.CRM-originated valuation and enquiry references
Approved agent reviews contact and next action
Time-stamped process receipt, without central client PII
This presentation describes Kadpex’s intended architecture and capabilities. Features are not represented as production-available, independently certified or regulator-approved until the necessary tests and reviews are completed. Country selection does not establish legal jurisdiction or staff authority.