Repair reports, visitors, payments and notifications use their own accounts, making it difficult for tenant staff to know where to handle them. The unified entrance should first sort out the relationship between tenants and personnel, and then display matters according to positions to avoid a shared account giving all personnel the same permissions.
How to arrange records and operations
Tenant administrators maintain the personnel of their unit within the scope of authorization, and business roles determine which matters can be submitted, viewed or confirmed. Off-duty accounts will be deactivated in a timely manner and will be transferred to designated personnel. The readable range and validity period of notification records, fees and contract information are only available to essential positions.
The relationship between personnel and tenants should be valid for a period of time. When the same person represents multiple units, the current identity is switched, and the page clearly displays which unit is handling matters. New personnel added by tenant administrators are also subject to scope restrictions and cannot grant internal management rights within the park on their own. Set visible roles separately for fees, contracts, and general notifications. The to-do transfer records the original person in charge and the new person in charge. Deactivation of the off-duty account will not cause the process to be lost. When a notification requires confirmation of reading, a confirmation record is retained, but the reading action does not automatically mean that the business action required by the notification has been completed.
Specific scenarios that need to be checked
For example, administrative staff handle visitors, financial staff check bills, and test whether the menus and interface ranges of the two accounts are consistent. Mobile links also check login and authorization. The platform displays to-do items in a centralized manner, but should not force a set of approval steps for different matters and retain the business’s own processing rules.
