Demonstration environment

One demonstration portfolio. Distinct views for each role.

Every person in the demo sees only what their own job allows — the same scoping a real agency would get. Interactive sign-in requires individually issued access; this page is not a one-click tour. Permissions are checked beyond the screen. All people, properties and certificates are demonstration records, not customer data.

Agency owner

The whole agency workspace for one sample letting agency.

  • Dashboard, portfolio, landlords, tenancy management
  • Team & branches, invitations, billing (test mode)
  • Ask Letify360, agency-system connections (test mode)

How to enter: Interactive access must be issued separately.

Compliance manager

Everything compliance, nothing commercial.

  • Certificate inbox: upload, read, review, accept
  • Evidence log and export; registration exposure view
  • Cannot change money, team or connections

How to enter: Interactive access must be issued separately.

Operations staff (internal)

The internal operations desk — a separate sign-in context from any agency.

  • /staff/board: every agency's queues, clocks, escalation
  • /staff/intake: platform exceptions needing a person
  • /staff/billing: payment exceptions for internal close

How to enter: Issued an internal staff role by the platform, never self-granted.

Landlord

One landlord's own properties. Never another landlord's, never agency powers.

  • Their own properties and safety record dates
  • Access limited to their own records, not other landlords

How to enter: The agency grants access to their email; claimed at first sign-in via /portal.

Resident

One tenancy. Their home only.

  • Their own tenancy, its safety records and dates
  • The report route — with hard stops for gas, CO, sparks, water near electrics and burning smells

How to enter: The agency grants access to their email; claimed at first sign-in via /portal.

Engineer

Only the jobs assigned to them.

  • Their own job list, appointments and status
  • Their own qualifications and accreditations

How to enter: Their account is linked to their engineer record by the operator.

Privacy & data lead

Data-protection operations for the agency.

  • Draft data-processing terms and named acceptances
  • Retention rules, legal holds, data requests, suppliers
  • A removal request is refused in writing while a hold stands

How to enter: Signs in at /auth; the privacy screen is permission-gated.

Notes for the demonstration

  • Fictional records illustrate the workflows, not live service fulfilment. Payment and external communication behaviour must be checked for the relevant environment.
  • Compliance is evidence-based: a certificate counts only when it is backed by a stored original and a recorded human decision.
  • Consequential actions wait for a named person to confirm them — including anything Ask Letify360 proposes.
  • Wording in safety advice, penalties and legal deadlines is marked unverified and must be reviewed before any real customer.