Owners and shares
It will hold the register of each building, who owns what and with which ownership share.
On the roadmap
Module in development
Property communities
The owners, the meetings and the ownership shares that are missing, on top of the issuing, collection and repairs that already work.
Property communities is an iERP module in development for property management: it will cover the register of owners with their ownership shares, meetings and their resolutions, recurring dues and special levies with their apportionment. It cannot be activated in any workspace yet. Issuing and collection already run on Finance today and building repairs on Support.
What it does
What Property communities will cover
Written in the future tense on purpose: this is what the module will solve once it exists, not what it does today.
Meetings and resolutions
It will record the notice, the attendance, the vote and the resolution with its minutes.
Dues and special levies
It will work out the apportionment of recurring dues and of a special levy by ownership share.
Building repairs
It will turn a resident's report into a ticket with an owner and a status, leaning on Support.
How the AI runs it
What you will be able to ask it
Once Property communities is in production you will be able to ask for the apportionment of a levy. Today the agent already handles outstanding dues and repairs.
The agent reads, proposes and asks for confirmation before writing, and every action is logged in the audit trail as an AI action. This module's own actions will ship with the module.
Open an incident for the lift breakdown in block 3.
soporte.ticket_crear incident opened
I have the incident ready with an owner assigned, and here are the outstanding dues from Finance. Meetings, ownership shares and levy apportionment will come with this module.
- Which dues are still unpaid this quarter?
Works with
What Property communities will build on
The due issued and the payment collected already belong to Finance, the resident's breakdown is already a Support ticket, and the reminders for due dates and meetings are chained in Automation. All three are in production and share database, permissions and agents.
Finance
In production
Invoicing with your own series, partial payments, treasury forecasting and a chained invoice register.
View module
Support
In production
Tickets with SLAs in minutes, reply templates and the customer conversation over email, fully traced.
View module
Automation
In production
Flow canvas, triggers and steps with human intervention across modules.
View module
On the roadmap
What exists today and what is missing
The whole module is missing: there is no register of owners, no meetings and no apportionment by share in production, and it cannot be activated in any workspace. Issuing, collection and repairs do work today.
- What it will cover: owners and ownership shares, meetings with their resolutions, recurring dues and special levies.
- What you can already do today: issue and collect dues with Finance, handle repairs with Support and send due-date reminders with Automation.
- When it lands: we give no date, because we do not have one. It is prioritised by real demand, so asking for it moves the queue.
Questions about Property communities
What people ask before deciding.
Partly. Finance already issues and collects recurring dues and Support already handles building repairs. The register of owners, the meetings and the apportionment by share are what this module will bring, and it is in development.
Tell us your case and we prioritise
Half an hour with your real buildings. In the meantime, the Professional plan already includes Finance, Support and Automation, which cover dues, repairs and reminders.