Security & privacy
Access and permissions in condominium software
Condominium management software is not a single archive where everyone sees everything: it is a system of roles, each with a defined data perimeter. The administrator has full access to the buildings they manage, the unit owner sees their own account and the communications addressed to them, and an office collaborator works only on assigned files. This separation is not a technical footnote: it reflects the data minimization principle under GDPR and the administrator's accountability to the assembly for record keeping. Understanding how these access levels are structured helps management firms choose the right tool and helps owners understand what they can actually see and request.
The typical roles in condominium software
Most condominium software structures access on three or four distinct levels. The administrator, or the firm representing them, has full visibility over the buildings they manage: budgets, meeting minutes, supplier contracts, complete owner registries, and cash movements. This is the role with the greatest responsibility, since the administrator is accountable to the assembly for proper record keeping under Italian condominium law.
The unit owner has restricted, personal access: their own debit and credit position, the installments charged to them, the assembly documents they are entitled to consult, and communications addressed to them or to the whole building. They do not see the accounting position of other owners, nor sensitive personal data of third parties.
A third level concerns office collaborators: secretaries, trainees, or external technicians assigned to a specific matter. Good software lets the administrator assign them only the buildings or functions relevant to their task, without opening the entire portfolio managed by the firm.
What a unit owner actually sees
An owner accessing their personal portal is entitled to consult their own accounting position, assembly minutes, the building regulation and, generally, documentation directly concerning them as a participant in the shared property. This right of access reflects the administrator's obligation to keep the accounting register and make it available for consultation.
A well designed permission structure distinguishes between aggregated building data, such as the total budget or the cost allocation plan, which remain visible to all owners because they are instrumental to management transparency, and personal data of other owners, such as their individual debt position or private contact details, which should not be exposed without necessity.
Some software also gives owners limited operational functions, such as paying their own installment online or opening a maintenance request: even here the perimeter remains their own unit, never the entire building.
Least privilege applied to condominium management
The least privilege principle, borrowed from information security, translates in condominium management into a simple rule: every user should have access only to the data and functions strictly necessary for their role, nothing more. For an administrator this means being able to delegate a collaborator to a single building without exposing the entire managed portfolio, or limiting an external technician's access to only the technical documentation of their specific job.
Applying this principle concretely reduces risk in case of human error or compromised credentials: if an access is misused or stolen, the damage stays confined to the perimeter assigned to that role, rather than extending to the whole managed portfolio.
It is also a measure indirectly required by GDPR, which mandates minimizing data processing relative to its purpose: a firm managing dozens of buildings should be able to demonstrate that each collaborator sees only what is needed to perform their task.
What to check when choosing or evaluating software
Before adopting or keeping a condominium software it is worth checking a few concrete aspects of its access model: whether distinct collaborator roles can be created with permissions differentiated by building, whether owners log in with their own personal credentials rather than shared ones, whether there is traceability of who changed what and when, and whether revoking an access, for example at the end of a collaborator's assignment, is immediate and complete.
AmministraPro structures access following this logic of separated roles: the administrator manages the entire building portfolio with full visibility, unit owners access a personal area limited to their own position and relevant documentation, and collaborators can be enabled with permissions calibrated to the buildings actually assigned to them. Anyone evaluating the features and plans can check directly which access levels are available for their firm's size.
Frequently asked questions
Can a unit owner see the accounting position of other owners?
No. In properly configured condominium software, an owner sees only their own debit and credit position, the installments charged to them, and payments made. Individual accounting data of other owners remains confidential, while aggregated budget data, necessary for the management transparency required by law, is visible to all participants.
Who can modify accounting data and who can only view it?
Typically only the administrator and collaborators granted write permission can enter or modify accounting entries, installments, and budgets. Unit owners have read only access to their own position: they can view but not alter the data, which preserves the integrity of the accounting the administrator is accountable for to the assembly.
What happens to permissions when a collaborator's or administrator's assignment ends?
Good condominium software lets you immediately revoke a collaborator's access when the working relationship ends, without having to change shared passwords. When an administrator is replaced, the incoming administrator should be able to access the building's documentation under the ordinary handover rules, while the outgoing administrator loses operational access.
Are permissions differentiated by building useful for a firm with a single administrator?
Yes, they are useful even for a small firm, since external collaborators are often engaged for specific tasks, such as a technician for a job on a single building or a secretary for document management. Being able to limit these figures' access to only the relevant buildings, rather than the entire portfolio, is a useful minimization measure regardless of firm size.
How does AmministraPro manage roles and permissions among administrators, collaborators, and owners?
AmministraPro separates access by role: the administrator has full visibility over the managed buildings, collaborators can be enabled with permissions limited to the buildings actually assigned to them, and owners access a personal area showing only their own accounting position and relevant documentation. Details on available features and plans can be found on the features and pricing pages of the site.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.