WHY IS THIS FEATURE NEEDED
In a large community with multiple towers, each Tower may be registered as an Association (separate legal entity). Each Association becomes a member of another legal entity, which is the Federation.
Owners and Residents primarily pay Dues to the Association relevant to their respective Tower.
Association may pay a Membership contribution to the Federation.
Federation may be responsible for the maintenance of Assets and Amenities common to all the Associations - e.g., Common Roads, Clubhouse, Periphery Gates etc.
HOW DOES THIS FEATURE WORK
On ADDA below is how this Organization Structure can be deployed as a Parent Child mode:
1. Each Association has its own ADDA portal. This can be considered as the Child ADDA. This means it has its own Books of Accounts, Unit Data, Resident Data, etc. It will be seeing its own BalanceSheet, generating automatic Maintenance Invoices, and collecting payments from Residents to its own Bank Account. It can also set up booking for certain facilities available only for the specific tower. (e.g., tower level party hall)
2. The Federation has its own ADDA portal considered as the APEX ADDA. It comes with its own set of Books of Accounts. Any Unit or Resident added to the Association ADDA (aka Child ADDA), automatically shows up on the Federation ADDA (aka APEX ADDA). This way the Federation ADDA always has a synchronized and LIVE Database of all Units and Residents across all the Towers.
3. If the common Clubhouse is under the Federation, then it can be setup in the Facility Booking of the APEX ADDA. Setting up any Facility here, automatically shows the facility for booking on the ADDA App of all Residents in all Towers. Residents can book the facility and any payment directly goes to the Federation bank account configured, and accounting entries automatically happen in the Books of Accounts of APEX ADDA.
BENEFITS:
- Viewing and monitoring a consolidated facility booking calendar
Billing and Accounting automatically happen into the Apex ADDA
Residents from all child ADDAs can book facilities
4. If the common Gates are under the Federation, then GateKeeper can be setup for the APEX ADDA. Then the Visitor entries made at APEX ADDA level automatically notify the Relevant Resident in the Relevant Tower. All other GateKeeper features such as pre-approved visitors also work in similar fashion.
BENEFITS:
- Check-in of visitors and staff can be done for any association at the gate.
Residents from all child ADDAs can view the list of their visitors and staff.
In a single GateKeeper device, all towers ( associations) data can be fetched for the GK operations.
Note: Staff and vehicle data will be added in the APEX ADDA for the common Gate operations.

Note: For Support with deploying Apex ADDA please raise a Support Ticket on support@adda.io
Author: San