When a condominium building considers adding cameras, https://realtytimes.com/new-headlines/cctv-in-elevators-and-common-areas-property-manager-responsibilities the first question is often, “Where should we put them?” A more useful question comes first: What security question does this camera answer? If nobody can explain the purpose, the building may be collecting footage without a clear reason—and creating privacy, cost and governance problems along the way.
So who decides the rules: the condo or homeowners’ association (HOA) board, or the property manager? In most buildings, the board sets policy and approves significant decisions, while the manager carries out the approved process and operates the system within defined limits. The exact division depends on local law, the association’s governing documents, contracts and any privacy or data-protection rules that apply.
This guide explains how to approach condo CCTV governance, from camera approval and field of view to access controls and routine deletion. It also covers an easy-to-miss point when reviewing online material: if a scraped article lists no prices, do not fill in the gap with invented figures. Get current, comparable quotes for your own building.
Start by separating policy from day-to-day operation
CCTV decisions are rarely the responsibility of one person alone. A well-run arrangement distinguishes between who has authority to set the rules and who is permitted to perform operational tasks.
Role Typical responsibilities What the role should not assume HOA or condo board Approves the purpose, policy, budget and major system changes; oversees compliance and reviews significant incidents. That approval means every board member can watch live or recorded footage whenever they want. Property manager Implements board-approved procedures, coordinates contractors, maintains records and handles authorised requests. That managing the building gives them unrestricted authority to install cameras or disclose recordings. Security staff or contractor May monitor or retrieve footage for a defined operational purpose under written instructions. That technical access is permission to browse, copy or share clips informally. Residents and other users Can raise concerns, report incidents and receive required notices or information about the policy. That being an owner or resident automatically grants access to footage of other people.The board is generally the right body to decide whether surveillance is needed, what it is intended to achieve and what safeguards apply. The manager may recommend practical options and administer the system, but should not be left to invent policy after the cameras are already installed.
What does “board approval” need to cover?
HOA board camera approval should be more than a brief vote to “add security cameras”. The board should have enough information to make a reasoned decision and record it in meeting minutes or an approved resolution. Before authorising a new installation or a material change, it should consider:
- The specific safety or security concern being addressed, and any evidence of that concern. Whether a less intrusive measure could work, such as improved lighting, access control, repairs or staff procedures. Which areas need coverage—and which areas should remain outside the camera view. Who will be able to view live feeds, retrieve recordings, export clips or approve disclosure. How long footage will be kept and how routine deletion will be checked. How residents, visitors, staff and contractors will be informed. What the system will cost to install, operate, maintain and eventually replace.
Local law and the association’s documents may impose additional requirements. Some decisions may require a particular type of board vote, member consultation, notice or legal review. Managers should check those requirements rather than assume that a standard purchasing approval is enough.
Agree on purpose before choosing cameras
Data minimisation is a practical principle: collect only what is necessary for a defined purpose. A building should not install cameras “just in case” or use them as a general way to keep an eye on residents. A camera’s purpose should be specific enough to guide placement, access and retention.
For example, a board might identify repeated unauthorised entry through a particular garage gate. That is a more useful purpose than “improve security everywhere”. It allows the building to ask whether a camera at the entrance would help, whether access logs or gate repairs should be tried first, and whether recording the whole garage is genuinely necessary.
Define what the system is not for
A clear policy should also set boundaries. Depending on local requirements and the building’s needs, it may rule out using footage for routine monitoring of residents, settling neighbour disputes unrelated to safety, tracking staff performance without an approved basis, or sharing clips for entertainment or social media. Restrictions should be explicit, not left to each operator’s judgement.
Camera placement and field of view: keep the frame tight
Even a camera installed for a legitimate purpose can capture more than the building needs. Its position, lens, zoom and angle can affect the privacy of residents, visitors, staff and neighbouring properties. Camera placement should therefore be reviewed on site, not decided from a floor plan alone.
Ask whether the camera can be angled or masked to exclude unnecessary areas. A garage entrance camera may need to record the gate and immediate approach, not every parking bay. A lobby camera may be able to cover the entrance without pointing into a reception workstation or private doorway. Avoid audio recording unless there is a specific, lawful and reviewed reason; audio can be more intrusive than video.
Use a placement checklist
- State the security purpose for each camera, not just for the system as a whole. Mark the intended field of view on a plan and verify it on site. Check whether neighbouring homes, windows, private balconies or unrelated premises are visible. Limit capture of desks, computer screens, keypads and documents. Use privacy masking or camera adjustment where available and appropriate. Document who reviewed the final view and when it was last checked. Reassess coverage after renovations, changes to landscaping or changes in building use.
Do not treat zoom or “we can crop it later” as a complete privacy safeguard. If unnecessary areas are being recorded, the better fix is usually to adjust the camera or configure masking at the source.
What does “property manager operates CCTV” mean?
The phrase property manager operates CCTV should describe a controlled operational role, not open-ended discretion. A manager might arrange maintenance, check that the recorder is working, respond to an authorised incident request and keep an access log. The manager should follow board-approved instructions and applicable law when doing so.
Access should be based on job need. A sensible policy names roles or individuals who may access the system, rather than granting access to everyone on the onsite team. Where the technology supports it, use individual accounts, strong authentication and role-based permissions. Avoid shared logins: they make it difficult to establish who accessed footage and why.
Control viewing, exports and disclosure
Live viewing, playback, exporting a clip and disclosing a clip are different actions. Each should have a defined authorisation process. A building may, for example, require a written request, a stated incident or purpose, approval by an authorised person and a record of the decision. Emergency procedures should be clear too, so that staff are not left guessing under pressure.
Always ask where exported clips end up and who can open them. A clip saved to a personal phone, emailed between staff or placed in a broadly accessible shared folder can quickly escape the building’s controls. Use an approved, access-restricted storage method; record the recipient and reason for each export; and set a deletion date. Do not send raw clips around casually.
Retention periods and routine deletion
There is no single retention period that suits every building or every jurisdiction. The board should set a period that is no longer than necessary for the stated purpose, while checking any legal, regulatory, insurance or contractual requirements that apply. Keeping footage indefinitely because storage is available is not a retention policy.
Routine deletion should be a normal, documented part of system operation. The policy should say when footage is overwritten or deleted, who is responsible for checking the process and what happens if the system or storage configuration changes. A building may need a narrowly controlled exception to preserve a relevant clip for a reported incident, legal obligation or authorised investigation. That exception should not become a reason to keep all footage longer.
Set and approve the ordinary retention period. Configure automatic overwrite or deletion where possible. Define who can place a relevant clip on hold and on what grounds. Record the clip’s location, access permissions and review date. Delete the preserved clip when the reason for keeping it ends, subject to applicable requirements. Periodically verify that deletion and access controls are working as intended.Keep a useful access and disclosure log
A log helps the board demonstrate that access is controlled and helps the manager respond consistently to requests. It need not be complicated, but it should record enough to reconstruct what happened. Include:

- Date and time footage was viewed, retrieved, exported or disclosed. Name or role of the person who accessed it. The stated purpose and relevant incident or request reference. Who authorised the action, where required. What was exported, where it was stored and who received access. The scheduled deletion or review date.
Disclosure requests can raise privacy and legal questions, especially when footage shows people other than the requester. Do not promise a clip or send it immediately. Follow the building’s approved process, check applicable law and seek advice from the association’s counsel where appropriate. A request from a resident, insurer, police service or lawyer may need to be handled differently depending on the circumstances and jurisdiction.
Address costs without inventing prices
Some scraped or reused articles mention CCTV without listing any prices. That omission does not justify guessing at a system cost. Prices vary with the number and type of cameras, cabling, storage, installation conditions, monitoring arrangements, maintenance and local supplier rates. Treat an absent price as absent information—not as a figure to estimate and present as fact.
For a board decision, obtain current quotes based on the same written specification. Ask suppliers to separate installation, storage, licensing, support, maintenance and replacement costs. Confirm whether quoted storage settings support the board’s retention policy, who controls administrator access, and how footage can be exported securely. Compare the ongoing cost as well as the initial purchase price.
A practical approval process for boards and managers
Define the concern. Document the incident pattern or risk and the outcome the building wants. Check alternatives. Consider lighting, locks, access control, repairs or staffing changes before adding surveillance. Review authority. Check governing documents, contracts and applicable legal requirements. Specify proportionate coverage. Identify camera locations, fields of view, exclusions and any masking. Approve written rules. Set access roles, permitted uses, disclosure steps, retention and deletion procedures. Record the decision. Keep the board’s rationale, approvals and system specification with association records. Train operators. Make sure staff and contractors understand the limits and know how to escalate requests. Review regularly. Check whether the purpose remains valid, whether the cameras are properly aimed and whether access logs and deletion work.Common mistakes to avoid
- Installing cameras “just in case”, with no specific purpose. Assuming the manager can set policy simply because they manage the building. Letting board members, staff or contractors browse footage out of curiosity. Recording broad areas when a narrow field of view would meet the need. Keeping footage indefinitely or failing to check routine deletion. Emailing raw clips or leaving exports in shared folders with no access limit or deletion date. Approving a supplier proposal without clarifying ongoing costs, access or storage arrangements. Failing to review the system after building changes or a change in purpose.
The bottom line
In a well-governed condo, the HOA or condo board normally sets the CCTV purpose, policy and approval boundaries; the property manager implements and administers those decisions within a defined role. The board should not micromanage every authorised operational task, but it should never leave core questions—why cameras are used, what they capture, who can access footage and when it is deleted—to informal practice.

Keep the system proportionate, keep the field of view tight, document access and disclosure, and make routine deletion part of the operating process. Above all, be able to explain what security question each camera answers—and why the building needs the footage it collects.
Share this guide
Share on Facebook | Share on X (Twitter)
Note: This article provides general operational guidance, not legal advice. Requirements differ by location and by the association’s governing documents; consult qualified local counsel when needed.