We are introducing what we are calling an ‘interest’ layer on top of a requirement.
This new layer will act as a wrapper around a requirement allowing users to curate a version of the requirement bespoke to a particular disposal/interest schedule. For the avoidance of doubt, this will not change the underlying requirement, rather create a bespoke layer on top.
This will be useful in the following circumstances:
When you have joint agents and you wish to keep certain information private
The requirement will be your internal version (private) and the interest layer will be what is collaborated around
When you are collaborating with a landlord and you wish to curate the information to better suit the occassion, while keeping the internal requirement untouched
Please authenticate to join the conversation.
General Feature Request
7 months ago

Chris from Kato
Get notified by email when there are changes.
General Feature Request
7 months ago

Chris from Kato
Get notified by email when there are changes.