What Public Applications does in Proplix
Public Applications is part of Proplix Applicants, Renters & Pre-Tenancy and is designed to accept structured applications from prospective renters through a controlled public entry point. It keeps submitted applicant details, source property and the relevant consent context against the applicant and property context that gives it meaning.
Within the wider Applications & Invitations workflow, Public Applications supports application intake, controlled invitations and the handoff from public interest into a structured pre-tenancy record and should lead towards a traceable application inside the workflow rather than an isolated inbox message without rebuilding the same information from public forms, inboxes or spreadsheets.
Why this capability matters before tenancy onboarding
Public Applications matters because a prospect needs to apply without first having an internal staff account. If submitted applicant details, source property and the relevant consent context is scattered across separate records, the next colleague may have to work out which applicant, property and version is current before acting.
A structured Public Applications record supports a traceable application inside the workflow rather than an isolated inbox message while reducing the risk that an application loses its property context, arrives through an unmanaged route or remains accessible through an invitation that should no longer be usable and keeping human review, privacy controls and the organisation's fair decision process intact.
Where Public Applications adds operational value
For Public Applications, this section focuses on accept structured applications from prospective renters through a controlled public entry point while keeping the applicant and property context visible.
The point in the journey
A prospect needs to apply without first having an internal staff account. Public Applications gives that moment a defined place so the applicant and property relationship does not get lost.
The outcome to protect
A traceable application inside the workflow rather than an isolated inbox message. Keep submitted applicant details, source property and the relevant consent context connected to the application so the authorised next action is clear without reconstructing the record from separate sources.
How Public Applications fits into the workflow
The exact screen and permission path for Public Applications depends on the user's role, but the applicant, property and application context should remain connected throughout.
- 01
Begin from the correct application route
For Public Applications, start from the property, invitation or public route relevant to a prospect needs to apply without first having an internal staff account. That makes the applicant/property relationship explicit before submitted applicant details, source property and the relevant consent context is submitted.
- 02
Capture what this capability needs
Use Public Applications to record submitted applicant details, source property and the relevant consent context. Collect only what supports accept structured applications from prospective renters through a controlled public entry point, and make any genuinely optional detail clear to the applicant.
- 03
Make the record understandable
An authorised colleague reviewing Public Applications should be able to see what submitted applicant details, source property and the relevant consent context means and how it relates to a traceable application inside the workflow rather than an isolated inbox message without rebuilding the story from another system.
- 04
Control the application state
Before Public Applications progresses, confirm that its submission or invitation state is still valid for a traceable application inside the workflow rather than an isolated inbox message. For Public Applications, an expired, revoked or incomplete route must remain visibly different from the authorised state required for a traceable application inside the workflow rather than an isolated inbox message.
- 05
Hand off deliberately
If Public Applications reaches its intended outcome — a traceable application inside the workflow rather than an isolated inbox message — carry forward the applicant and property context needed by the next authorised stage instead of copying the whole application into another uncontrolled record.
What Public Applications helps the team control
Connected applicant context
Public Applications keeps submitted applicant details, source property and the relevant consent context attached to the applicant and property context in which it is needed.
Structured information
Instead of leaving submitted applicant details, source property and the relevant consent context in free-form messages, Public Applications gives it a repeatable structure that supports accept structured applications from prospective renters through a controlled public entry point.
Application state clarity
Public Applications keeps the relevant submission or invitation state visible, so a traceable application inside the workflow rather than an isolated inbox message is not confused with an earlier public-entry or staff-invitation step.
Workflow continuity
Public Applications can carry the context needed for a traceable application inside the workflow rather than an isolated inbox message into the next authorised stage without asking for the same facts again.
What Public Applications looks like in practice
Consider a case where a prospect needs to apply without first having an internal staff account. The applicant or authorised team member uses Public Applications from the relevant property or application context, so submitted applicant details, source property and the relevant consent context is captured against the record that will actually be reviewed.
A second authorised colleague can see what was provided, identify missing detail and, if the case progresses, hand only the context needed for a traceable application inside the workflow rather than an isolated inbox message into the next authorised stage.
How to introduce Public Applications into a live applicant workflow
For Public Applications, implementation should keep information proportionate to its purpose, clearly owned and dependable through corrections, exceptions and handoffs.
Give Public Applications a clear owner before rollout. Decide who is responsible for submitted applicant details, source property and the relevant consent context, which values are applicant-supplied and which authorised staff may amend or review them.
Keep Public Applications proportionate to accept structured applications from prospective renters through a controlled public entry point. Make optional detail clear and protect public entry points with appropriate access, transport and rate controls.
Test the normal case and realistic exceptions such as missing information, a correction after submission, an unavailable property or a revoked invitation before handing the context into the next workflow.
Who works with Public Applications before a tenancy is created
Public Applications supports the authorised people who provide, organise, review or progress this part of the applicant journey.
Keep Public Applications data, decisions and permissions aligned
Public Applications can involve personal or financial information. Apply least-privilege access, privacy notices, retention rules and lawful data handling to submitted applicant details, source property and the relevant consent context.
A structured record improves consistency but does not verify submitted applicant details, source property and the relevant consent context automatically; authorised users should correct material errors before relying on it.
Any decision informed by Public Applications should remain fair, explainable and limited to the legitimate purpose of accept structured applications from prospective renters through a controlled public entry point, while preserving the same applicant and property identity across handoff.
Related features in Applicants, Renters & Pre-Tenancy
These pages sit close to Public Applications in the wider application and pre-tenancy architecture.
Technical flow & related Help Centre guides
Start with the primary guide for this capability, then use the related maintained guides for the surrounding workflow, evidence, access or handoff.
Questions about Public Applications
What is Public Applications used for in Proplix?
Public Applications is an Applicants, Renters & Pre-Tenancy capability for accept structured applications from prospective renters through a controlled public entry point. It keeps submitted applicant details, source property and the relevant consent context connected to the relevant applicant and property journey.
When is Public Applications most useful?
Public Applications is most useful when a prospect needs to apply without first having an internal staff account. In that situation, the intended operational result is a traceable application inside the workflow rather than an isolated inbox message.
Who should be able to access Public Applications?
Access to Public Applications should be limited to applicants and authorised staff who genuinely need submitted applicant details, source property and the relevant consent context for accept structured applications from prospective renters through a controlled public entry point, according to your organisation's permissions and data-handling policy.
How does Public Applications connect to tenant onboarding?
If Public Applications is authorised to progress, the applicant and property context needed for a traceable application inside the workflow rather than an isolated inbox message can support a controlled handoff into the separate tenancy-onboarding workflow. Capturing submitted applicant details, source property and the relevant consent context does not by itself create tenancy approval or a contract.
Explore how Public Applications fits your applicant journey
See Public Applications alongside property interest, application information, household context, affordability evidence, review and the later onboarding handoff. A walkthrough can focus on your actual lettings process rather than a generic software tour.