Choosing software
Condominium software for an associated practice
An associated condominium management practice is not simply a single administrator with an extra desk. Several professionals share clients, mandates and responsibilities, and each often manages part of the portfolio independently. The software chosen in these cases has to satisfy two needs at once: give each partner operational freedom over their own condominiums, while ensuring that nobody can alter or view data that is not theirs. Software built for a lone administrator, with one account and all or nothing permissions, forces the practice to either share a password or give up traceability of who did what. People working together across multiple mandates need distinct roles, activity logs and a data structure that genuinely separates one client from another.
Checklist for an associated practice
- The software provides distinct named accounts for each professional in the practice
- Permissions can be assigned per individual property, not only for the whole practice
- An activity log shows who recorded or modified what
- Data stays linked to the practice rather than to the individual user who entered it
- Access to owners personal data can be limited to those who genuinely need it
- Transferring a mandate from one partner to another does not require manual data migration
- Assembly calendars and deadlines are shared among the professionals following the same property
- Reporting lets each partner see the status of their own portfolio without asking colleagues
Why a single account is not enough
In a sole practice, a single login is an acceptable inconvenience. In an associated practice it becomes an operational risk: if every professional logs in with the same credentials, there is no way to know who recorded an expense, who modified an allocation plan, or who responded to a resident. In case of a dispute, the assembly or the individual owner has the right to know who acted on behalf of the practice for that mandate, and Article 1129 of the Italian Civil Code already imposes transparency obligations on the administrator toward owners that an internally opaque system does nothing to help satisfy.
Software suited to an associated practice provides named accounts for each professional, with an activity log recording who did what and when. This is useful not only for internal accountability among partners, but also to respond precisely if a resident asks for details about a bookkeeping entry or a message that was sent.
Differentiated permissions by professional and by property
In an associated practice, not everyone needs to see everything. One partner may follow a set of properties in one area, another may handle properties currently in litigation, and a junior collaborator might only need read access or access limited to reporting. Good software lets permissions be assigned not generically across the whole practice, but property by property or group by group, so each professional sees and works only on the mandates they are responsible for.
This also matters for the practice internal administration: whoever handles secretarial work and communications does not necessarily need access to the accounting, and whoever manages the accounting does not necessarily need to be able to modify the owners registry or the assembly minutes. Granular permissions reduce both errors and the chances of internal friction.
Client data separation and mandate continuity
An aspect often overlooked is separation between the practice clients. If a partner leaves the practice or a mandate is transferred from one professional to another, the property data (financial statements, minutes, communications, technical documentation) must remain intact and accessible to the practice as a whole, not tied to the individual who entered it. Software organized around the organization, rather than around a single user, prevents a handover between colleagues from becoming a service continuity problem.
The processing of owners personal data under the GDPR also needs to be kept in mind: several professionals process the same data on behalf of the same data controller, the practice itself, so a system is needed that tracks access and limits visibility to those who genuinely need to process that data for the mandate they follow.
What to evaluate in practice
Beyond permissions, it is worth checking how the software handles day to day collaboration between professionals: shared assembly calendars, assignment of maintenance tickets or resident reports to a specific partner, and reporting that lets each professional see the status of their own portfolio without having to ask colleagues for updates.
AmministraPro is organized to manage several professionals within the same practice, with roles and permissions that can be assigned per property, so each partner works on their own mandates while the practice keeps a single, consistent data set.
Frequently asked questions
Does every professional in the practice need a separate account, or is a shared login enough?
A separate account for each professional is strongly recommended. A shared login makes it impossible to distinguish who carried out a given action, which complicates both internal accountability among partners and the response to any dispute from residents, who under Article 1129 of the Italian Civil Code have the right to clear information about the administrator conduct. Software with named accounts and activity logs solves this problem at the root.
How are permissions managed when each partner follows different properties?
The software should allow permissions to be assigned per property or per group of properties, not only generically across the whole practice. This way each professional sees and can modify only the mandates they follow, reducing both the risk of errors and the chance that a partner accidentally acts on a property that is not theirs. AmministraPro allows roles and permissions to be assigned at the property level to handle exactly this scenario.
What happens to a property data if the professional who managed it leaves the practice?
If the software is organized around the organization rather than around individual users, the data (financial statements, minutes, communications, documentation) remains owned by the practice as a whole, not by the departing professional. A new partner can take over the mandate without losing history or having to reconstruct documentation, ensuring continuity for the property being managed.
Does sharing data among several professionals in the practice raise privacy concerns toward residents?
It needs to be handled carefully because several people process personal data on behalf of the same data controller, the associated practice. The software should limit data visibility to those who genuinely need it for the mandate they follow and keep an access log, consistent with the GDPR principles of purpose limitation and data minimization.
Can software designed for a sole administrator still work for a small associated practice?
It can work in an early phase with just two professionals who trust each other, but it becomes a limitation as soon as the practice grows or mandates multiply, because traceability of who acted on what is missing. It is preferable to choose software designed for multiple users with distinct roles from the start, to avoid a complicated migration once the practice expands.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.