Feature/Function | Description | Considerations |
|
| |
| Residents will be able to select an access point that they can open using the App | Does this pose a security risk if the residents open gates for visitors without the visitor having a code and a headcount being conducted? |
- Define gate access per visitor type
| Enable estates to define which gates each visitor types is permitted to use. Corresponding gate access details will be added to the visitor code invitation | - Scanning service will need to interpret the visitor type
- Associated devices with gates
|
- Select visitor arrival point
| Residents will be able to select the greeting point for visitors based on a list of all their properties as well as common properties defined by the HOA | All locations should have mapping coordinates |
| | |
- Calculate cost and add to account
| Automatically add related charges to Resident account | - Estate will need to be on an online accounting system
|
| | |
| | None |
- Access extended personal information
| | Define what information is made available and what the update process and approval is |
| Display new feature Onboarding and Walkthrough screens | - Distinguish between new and returning users and display applicable information
- Include Admin ‘themes’ for each screen
|
| - Enable remote configuration of App features for each estate
- Enable each estate to configure interface images and colour scheme
| None |
- Auto-calculate Resident Age
| Display age breakdown | - DOB will need to be compulsory
- Not every minor is always added to the system
- Some Parents/Guardians may not want to provide the necessary information
|
| Track login dates and display in Management interface | None |
| Send a Push Notification to the resident on their birthday | This may be intrusive for some |