Frequently Asked Questions
Everything you need to know about setting up your society, resident apps, mobile money payments, and security protocols.
Residents create a visitor pass from the portal using the guest details and visit dates. Share the pass with the guest so authorized gate staff can check it against the society's visitor records. Your society should test pass scanning and check-in on its gate devices before relying on that workflow.
The payment methods available to your society appear in its portal. Stripe and MTN Mobile Money flows require merchant credentials, a supported currency and successful provider testing before live use. Other online providers remain unavailable until their integration is completed and configured. Cash and bank transfer entries require confirmation by an authorized finance user before they count as received payments.
Yes. Each society has its own memberships, permissions, accounting records and branding settings. A landlord can use one portfolio for accepted ownership links across societies. Any separate society web address requires hosting and routing configuration before it can be used.
Residents can submit an SOS alert with their unit and incident details. Your society must configure its response team and test the alert workflow on its devices. External notification delivery depends on configured providers; contact emergency services directly when urgent help is needed.
Import tooling is available for supported record types. Rehearse each import on staging, check the preview and reconcile the resulting records before importing live data. Timing depends on the data and hosting environment.
Onboarding time depends on record quality, configuration, training and acceptance testing. The setup screen tracks saved society details, created units and residents, billing setup and gate contact information.
Have a question not listed here?
Contact Our Support Team