What Public Agent Profile does in Proplix
Public Agent Profile is part of Proplix Landlords, Owners, Agents & Brokers and is designed to make the approved agent profile available in the relevant public presentation context. The capability keeps the stakeholder information tied to the relationship or account where it belongs rather than treating it as an unrelated contact record.
In practical terms, Public Agent Profile supports profile, privacy and verification control. The aim is to make identity, responsibility and presentation easier to understand for the next authorised user without requiring them to reconstruct the relationship from email, notes or local spreadsheets.
The stakeholder record is deliberately connected to the wider property operation. Where the same owner, agent or broker context is relevant to properties, listings, clients, assignments, communications or portals, Proplix can reuse that relationship while permissions and privacy controls govern what each audience can see.
Why this capability matters in stakeholder operations
Property operations become harder when stakeholder identity and responsibility are inconsistent. If public agent profile is maintained separately from the property or account relationship, teams spend time checking who is current, which profile is authoritative and whether the information is intended for internal or public use.
Profile information can serve several audiences, but those audiences do not need the same data. Public Agent Profile helps separate the internal operating record from public or stakeholder-facing presentation, reducing the temptation to expose fields simply because they are already stored.
Using Public Agent Profile inside Proplix is intended to reduce that ambiguity. A structured stakeholder model gives staff a clearer source for identity, assignment, profile and permission information while leaving legal, privacy and verification decisions with the authorised organisation.
Where Public Agent Profile adds operational value
This section focuses on the specific identity, relationship, privacy or administration context for this capability.
The privacy question
Public Agent Profile matters when an agent has been cleared for public presentation and users need a consistent published profile. The key distinction is between information the business needs operationally and information the stakeholder has been approved to present to another audience.
Verification is not visibility
A record can be verified without being public, and a public profile still needs an appropriate information set. Treat verification, privacy and presentation as related controls rather than one combined switch.
Minimise unnecessary exposure
If a field does not need to be shown in the current context, the safer design is not to expose it merely because it exists. Public and portal views should be deliberate subsets of the operating record.
How Public Agent Profile fits into the workflow
The exact screen and permission path depends on the stakeholder type and user role, but the capability remains connected to the same authoritative relationship record.
- 01
Start from the stakeholder record
Open the correct owner, agent or broker account before applying public agent profile so privacy or profile changes affect the intended record.
- 02
Review the audience
Identify whether the information is for internal staff, an authenticated stakeholder, or a public presentation context.
- 03
Apply the controlled profile state
Use public agent profile through the appropriate Proplix control rather than copying profile information into a separate public record.
- 04
Check connected views
Confirm that internal and public/profile views show only the information appropriate to their audience.
- 05
Review when circumstances change
Reassess privacy or verification state when profile information, evidence or the stakeholder relationship materially changes.
What this feature helps the team control
Controlled profile state
Use public agent profile to separate the stakeholder’s operating record from the information intentionally presented to others.
Privacy by context
Show only the profile information appropriate to the audience, relationship and permission state.
Verification visibility
Distinguish recorded information from information that has reached the organisation’s required verification state.
Reusable presentation
Keep approved profile information consistent wherever the stakeholder is shown.
Change control
Review public/private and verification changes deliberately instead of relying on informal conventions.
Data-minimisation mindset
Avoid exposing information simply because it exists in the underlying stakeholder record.
What this looks like in practice
A normal operational case starts when an agent has been cleared for public presentation and users need a consistent published profile. Instead of creating another general contact or leaving the relationship in a private note, the user handles Public Agent Profile from the relevant stakeholder account in Proplix.
The benefit becomes clearer when responsibility changes or another colleague takes over. The stakeholder identity, relationship and current state remain connected, while public/private presentation and access can still be controlled separately according to the user and context.
How to introduce Public Agent Profile into a live stakeholder operation
Good stakeholder management depends on a clear relationship model, an authoritative profile source and permissions that match responsibility.
Before rolling out Public Agent Profile, define the stakeholder model in plain language. Agree what counts as an owner, agent, broker, staff member and public profile, and which relationships can exist at the same time. Clear definitions prevent teams from creating duplicate records to represent the same person or organisation differently.
Choose the authoritative source for profile and relationship information. Decide which fields belong to the core stakeholder record, which belong to individual staff, which are used only for public presentation and which should remain permission-controlled. That separation is especially important where personal or commercially sensitive information is involved.
Test the common case and the main exceptions. Useful scenarios include an owner with several properties, an agency with several staff, a broker assigned to several records, a stakeholder moving from private to public presentation and a staff member whose permissions are reduced after a role change.
After adoption, review duplicate stakeholder records, shared-account workarounds, inconsistent codes and cases where staff still track assignments outside Proplix. Those patterns usually indicate that the stakeholder model, permissions or administration rules need refinement rather than another isolated field.
Built for the people responsible for stakeholder relationships
Public Agent Profile is designed for authorised people who create, review, assign, present or rely on landlord, owner, agent and broker information.
Keep identity, privacy and permissions aligned
Public Agent Profile should follow the organisation’s real stakeholder relationships rather than forcing every person into a generic customer model. Owners, agents, brokers and their staff can require different permissions, profile states and operating responsibilities.
Personal and business information should be kept accurate and limited to what is needed for the relevant workflow. A field being available to Proplix does not mean it should be exposed to every user or public profile.
Permissions should follow least-privilege principles. Users who can change privacy, verification, assignments or staff access should be authorised for that responsibility, and access should be reviewed when roles or relationships change.
Where verification, privacy or public presentation is involved, Proplix supports structured workflow and evidence visibility but does not replace the organisation’s legal basis, privacy obligations, due diligence or professional judgement.
Related features in Landlords, Owners, Agents & Brokers
These related pages sit close to Public Agent Profile in the wider stakeholder 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 Agent Profile
Does Public Agent Profile make all stakeholder information public?
No. Public or account-facing profile views should expose only the information approved for that context. Internal stakeholder data remains subject to privacy, permission and data-minimisation controls.
Is verification the same as public visibility?
No. Verification records an operational review state, while public/private controls govern presentation. A verified stakeholder can remain private, and a public profile still needs appropriate data selection.
Who should change Public Agent Profile?
Only authorised users responsible for the stakeholder profile, governance or account administration should change privacy, verification or presentation state.
Does Proplix replace GDPR or privacy-law judgement?
No. Proplix supports controlled workflow and visibility. The organisation remains responsible for lawful processing, data accuracy, retention, privacy decisions and professional or legal advice where required.
Explore how this capability fits your stakeholder model
Proplix connects stakeholder identity, properties, assignments, permissions and presentation. A walkthrough can focus on your actual landlord, agent or broker workflow rather than a generic software tour.