The Owner Relationship Runs on Transparency, Not Volume
Owners do not want more communication. They want clearer communication. The portfolios that retain owners across renewal cycles are the ones that make ownership feel calm — a dashboard that shows the right numbers, an inbox that is not flooded with operational noise, and answers that arrive before the question has to be asked twice.
An owner portal is the single most effective tool for producing that feeling, and it is one of the most commonly misconfigured.
What Owners Actually Want to See
The ArkanPM owner dashboard leads with four things, in this order:
- Total units owned — the ground truth against which everything else is measured
- Occupancy breakdown — occupied versus vacant, color-coded so the eye lands on vacancy instantly
- Aggregated monthly income — a single clear number, not a list of line items
- Upcoming lease expirations within 90 days — the leading indicator of next quarter's income
These four panels answer the questions owners actually ask. Everything else — maintenance counts, work order throughput, SLA attainment — is supporting evidence, available on drill-through but not shouting from the first screen.
Owners do not log in to admire operational dashboards. They log in to confirm that their asset is performing and to find out what is coming next. Respect that.
Ownership Records: The Data Model Matters
An owner portal is only as good as the ownership data behind it. ArkanPM tracks ownership at the unit level with full detail:
- Ownership type — freehold, leasehold, or usufruct
- Share percentage — for co-owned units
- Title deed number and date — for provenance
- Acquisition details — purchase, inheritance, gift, or developer handover
- Acquisition price and disposal tracking — for the full lifecycle
This matters because the portal must show each owner exactly their share of income and occupancy — not the building's. A co-owner at 40 percent of a unit sees 40 percent of the rent in aggregated income; a freehold owner of a full floor sees the full floor's numbers. Share-aware reporting is table stakes for shared-ownership scenarios that are common in Gulf towers.
Individual vs. Company Owners
ArkanPM supports both individual and company owners with GCC-relevant fields — Emirates ID, passport, trade license number, nationality, power of attorney holder details, and banking information (bank name, account number, IBAN). Capture these fields once and let them populate downstream documents and payout instructions. Do not make owners re-enter their identity every renewal.
Financial Masking: The Unsung Hero
Here is the honest reality of multi-role property platforms: the same record is viewed by technicians, managers, owners, and vendors, and none of them should see the same fields. A technician does not need to see the purchase price of a compressor they are about to service. A vendor does not need to see the rent a unit is collecting. An owner does not need to see the cost breakdown of a maintenance job on their own unit, but they do need to see that it was completed.
ArkanPM implements this through attribute-based access control (ABAC) — specifically, financial data masking at the API layer. Technicians and operational staff never see cost fields, purchase prices, or sensitive financial data. The API strips those fields based on the requester's role before the data ever reaches the client. Even if the front-end were misconfigured, the protected fields are not on the wire.
The practical benefit for the owner portal is that you can expose financial data — rent collected, maintenance spend, aggregated income — to the owner role without the risk of that same data leaking to unintended roles through shared queries, shared components, or shared report templates. The guarantee lives at the API.
What to Hide, Not Just What to Show
An owner portal is a set of decisions about omission, not just presentation. Omit:
- Internal work-order notes — the comment thread has an internal flag for a reason. Keep internal notes internal.
- Vendor cost breakdowns — owners see that a job was completed for a given amount. They do not see the vendor's markup, the internal labor rate, or the parts cost.
- Cross-portfolio comparisons — an owner sees their own units. They do not see how their units compare to another owner's.
- Operational SLA metrics — unless an owner has explicitly asked, do not surface SLA dashboards on the owner portal. It invites questions about work you are already handling.
The rule: an owner portal answers ownership questions, not operational ones. Operational transparency belongs to the property manager; ownership transparency belongs to the owner.
Document Access on the Owner Side
Owners access their relevant documents through a dedicated document portal — title deeds, ownership records, lease documents associated with their units, and payment records. The access scope is driven by the unit ownership relationship, so when ownership changes, document access changes with it. New owners see documents relevant to the period from their acquisition forward; prior owners lose access to records that no longer concern them.
This is the sort of thing that looks obvious in description and is painful to retrofit into a platform that was not designed for it. Get it right up front.
RBAC Discipline: Do Not Improvise Roles
ArkanPM ships with eleven built-in roles. The Owner role is one of them, with a defined scope: portfolio and financial visibility for owned units. Resist the temptation to create "Owner Plus" or "Special Owner" custom roles for edge cases. Each custom role is a future permission audit waiting to happen.
When a genuine edge case arises — a family office that wants one login for a multi-owner structure, for instance — model it through ownership records and power-of-attorney relationships, not through a new role. The role system expresses authority levels; the ownership data expresses the structure. Do not conflate them.
Building-Scoped Assignments for Managers
Separate from the owner role, building managers see operational data scoped to their assigned buildings with temporal assignments (expiration dates). Combined with ABAC, this means your portfolio can safely onboard property-management professionals who see everything they need within their scope and nothing outside it — including the financial data masked by their role.
The Result
An owner who opens the portal on Sunday morning, sees the four numbers that matter, glances at upcoming expirations, confirms nothing is on fire, and closes the tab. That is the outcome. It is deeply unflashy, which is why it works.