Set landlord, tenant and supplier portal policies
Portal policies refine access for existing native client identities; they do not create a second identity or replace the property/job relationship.
Before you start
Portal policies refine access for existing native client identities; they do not create a second identity or replace the property/job relationship.
Follow these steps
- Find the stakeholder and confirm client ID, role and property/scope.
- Open Policy and choose Enabled or Disabled.
- Select the capabilities needed for that role; unchecked capabilities are saved as disabled.
- Choose Save portal policy.
- Have the intended stakeholder check their Property Flow workspace in their own session.
- Verify both allowed information and the actions that should be absent.
Check it worked
The exact stakeholder/property policy is saved. Supplier policies apply to their assigned jobs rather than an arbitrary property.
If something does not look right
Changing a landlord policy also requires native landlord management authority; tenant policy changes need tenancy authority; supplier policy changes need maintenance authority.
Questions and answers
What happens if no saved policy exists?
Eligible linked roles use the module’s default allowed capabilities. Review policies deliberately before rollout.
Does disabling Flow disable the whole customer account?
No. It controls the Flow workspace/policy; other native client access remains governed separately.
Can one client have more than one role?
Yes. Active links and native groups determine available roles. Review each relevant policy.