What Staff Permissions does in Proplix
Staff Permissions is part of Proplix Landlords, Owners, Agents & Brokers and is designed to control what authorised agent and broker staff can view or do within their assigned role. 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, Staff Permissions supports staff identity and least-privilege access. 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 staff permissions 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.
The problem grows with larger portfolios and multi-person agencies or brokerages. Shared accounts, manually tracked reference numbers, duplicate owner records and vague assignments make handover slower and can create privacy or access mistakes that are much harder to correct later.
Using Staff Permissions 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 Staff Permissions adds operational value
This section focuses on the specific identity, relationship, privacy or administration context for this capability.
The access decision
Staff Permissions is useful when different stakeholder staff need appropriate access without receiving the same permissions by default. Access should be based on the person’s actual responsibility, not simply on membership of an agent or broker organisation.
Individual accountability
Separate staff profiles and permissions make handover and review clearer than shared accounts. They also allow access to change when an individual’s role changes without disrupting the wider stakeholder account.
Review after change
A permission set that was correct at onboarding may become excessive later. Review access after role changes, staff departures and material assignment changes.
How Staff Permissions 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
Identify the staff member
Start from the individual staff record connected to the correct agent or broker account.
- 02
Define the working role
Confirm which responsibilities the person holds and which areas of Proplix they genuinely need.
- 03
Apply least-privilege access
Use staff permissions to provide the required access without granting unrelated capabilities by default.
- 04
Test the staff view
Confirm that the user can complete the intended work and cannot see or change information outside the role.
- 05
Review access over time
Update permissions when staff responsibility, employment or assignments change.
What this feature helps the team control
Role-scoped access
Use staff permissions to give stakeholder staff only the access required for their operational role.
Account linkage
Keep each staff member connected to the correct agent or business-broker account.
Clear responsibility
Make the person handling the relationship distinguishable from the wider organisation account.
Permission review
Support periodic review when staff roles, assignments or responsibilities change.
Reduced shared access
Avoid several people relying on one undifferentiated account where individual responsibility matters.
Audit-friendly administration
Keep significant access changes understandable to authorised administrators.
What this looks like in practice
A brokerage adds a new staff member who needs to view assigned property information and update the parts of the relationship they manage, but should not receive unrestricted account access. Staff Permissions keeps the individual attached to the correct organisation while allowing access to be defined for the role.
When that person changes responsibilities or leaves, the team can review the staff record and permissions without having to replace the entire broker or agent account. This gives the organisation a much cleaner handover and access-control process than a shared login.
How to introduce Staff Permissions 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 Staff Permissions, 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
Staff Permissions 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
Staff Permissions 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 Staff Permissions 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 Staff Permissions
What does Staff Permissions control?
It supports role-based access for staff connected to the relevant agent or broker account. The exact permission set should match the person’s operational responsibilities.
Should every stakeholder staff member receive the same permissions?
No. Least-privilege access is preferable. Staff should receive only the capabilities needed for their role, with changes reviewed when responsibilities change.
Can permissions be reviewed later?
Yes. Permission reviews are especially important after role changes, assignment changes, staff departures or a material change in the stakeholder relationship.
Does a staff profile replace the parent organisation account?
No. The staff profile represents the individual within the wider agent or broker relationship and should remain connected to that parent account.
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.