How the platform fits together

PropLink is one ecosystem with several front doors. Each kind of user gets the interface that fits the job they need to do. Underneath, everything shares the same data, so an action by a contractor on site shows up immediately for a manager at a desk and a leaseholder on their phone.

The pieces

There are six things to know about.

The main admin app

The primary interface for managers, accountants and administrators. This is where you set up sites, raise demands, reconcile bank statements and approve work. It is what most people mean when they say "PropLink".

Product modules

Inside the main app, your organisation turns on the modules it needs. Block Management, Facilities Management, Building Safety, Lettings, and the sidebar adapts to show only what is relevant.

ResidencePort

A self-service portal for leaseholders and tenants. They sign in, view their statement, pay an invoice, raise a request and read building notices. ResidencePort runs on its own subdomain so you can brand it for your organisation.

ContractorPort

A focused tool used by contractors who are invited to a specific work order. They open a link, submit their quotation, upload certificates and mark the work complete. It is not a general self-service portal, its scope is a single work order at a time.

BuildingThread

The golden thread portal for high-risk buildings under the Building Safety Act. It gives residents and the Building Safety Regulator structured access to building safety information. BuildingThread is **Coming soon**.

Facility Report mobile app

A native mobile app for site managers. Sign in with OTP, switch between assigned sites, log an issue with a photo, update a work order on site, respond to a ticket.

PropManager AI

The planned AI layer that sits on top of PropLink. Property managers will be able to ask questions in plain English and have actions drafted for them. PropManager AI is **Coming soon**.

How they talk to each other

Every interface, admin app, portal or mobile, reads and writes the same data. There is no duplicate database, no synchronisation lag, no manual exports.

A worked example. A leaseholder logs an issue in ResidencePort. The issue immediately appears in the Issues list on the site in the main admin app. A property manager picks it up, converts it into a work order and invites a contractor by email. The contractor opens the ContractorPort link, uploads a quotation and a certificate of insurance. The manager approves the quotation. When the work is done the contractor marks the work order complete and uploads photos as evidence. The manager closes the work order, and the supplier's invoice flows into the Bills workflow ready for approval. The unit's history shows the whole sequence with timestamps, no copy-and-paste anywhere.

Where each section of the docs maps to the platform

Authentication in plain English

Every user signs in once. Where they land depends on what they are:

• A PropLink staff user lands on the main admin app at your-org.proplinkcloud.com.
• A leaseholder lands on ResidencePort at your-org.residenceport.com.
• A contractor opens a single-use link to ContractorPort scoped to one work order.
• A site manager signs in to the Facility Report mobile app with a one-time password.

You can read about the moving parts in Subdomain architecture.