Comparison
Separate portals vs unified stakeholder portals
A unified stakeholder portal gives trustees, owners, tenants and your own staff one login into the same underlying records, while a separate-portals approach runs each group on its own tool or login that holds its own copy of the data. For most South African managing agents, unified wins on data consistency: a levy raised, a payment received or a maintenance job logged is visible to the right people in real time without re-keying or reconciling between systems. Separate portals can still make sense where one stakeholder group needs a specialist tool, or where you are mid-transition and not ready to consolidate. Below is an honest, criteria-by-criteria comparison so you can judge which fits your book.
| Regalis | separate portals | |
|---|---|---|
| Single source of truth | All stakeholders read and write against the same records, so a levy, payment or document appears consistently for trustees, owners, tenants and staff. | Each portal holds its own data; the same fact can show differently in different portals until someone reconciles or re-keys it. |
| Access control by role | One permission model decides what each role (trustee, owner, tenant, agent) sees of the shared data, scoped per scheme or property. | Each portal manages its own users and permissions, so access reviews and offboarding must be repeated tool by tool. |
| POPIA data handling | Personal data sits in one governed store with one set of access logs, which simplifies subject-access requests and retention under POPIA. | Personal data is duplicated across portals, so honouring access, correction or deletion requests means tracing every copy. |
| Admin effort | Information is captured once and flows to the relevant views, reducing duplicate entry across stakeholder groups. | Common items (contact changes, statements, documents) often have to be entered or uploaded in more than one place. |
| Reporting across stakeholders | Trustee packs, owner statements and arrears views draw from the same ledger, so figures tie back without cross-tool reconciliation. | Pulling a combined view means exporting from each portal and merging, with reconciliation risk between sources. |
| Onboarding new stakeholders | Adding a new owner or tenant grants the right scoped view from existing records, without standing up a separate account elsewhere. | A new stakeholder may need provisioning in a dedicated portal, with its own invite, login and data setup. |
| CSOS and scheme governance | Trustee and member views share the scheme's records, supporting consistent disclosure of levies and resolutions relevant to STSMA and the CSOS Act. | Trustee and member portals may hold separate copies, so governance disclosures must be aligned manually before they match. |
| Continuity if a tool changes | Stakeholder views are part of one platform, so a change in one area does not orphan a standalone portal's data. | Replacing or retiring one portal can strand that group's history and require a separate migration. |
| Cost and licensing | One platform licence covers the stakeholder views you switch on, avoiding several overlapping subscriptions. | Separate portals can each carry their own subscription, though you only pay for the specific tools you actually use. |
Where Regalis is strong
- One source of truth: a levy, payment, document or maintenance job is captured once and shown consistently to trustees, owners, tenants and staff.
- Simpler POPIA posture: personal data lives in one governed store with unified access logs, easing subject-access and retention obligations.
- Less duplicate admin: information flows to the right views automatically instead of being re-entered or re-uploaded per portal.
- Cross-stakeholder reporting that ties back to a single ledger, so trustee packs and owner statements reconcile without merging exports.
Where this approach can make sense
- A specialist standalone portal may offer deeper features for one group than a general platform's view of the same data.
- Separate tools can be adopted incrementally, letting you keep what works and avoid a single large migration.
- If one stakeholder group has very different needs, isolating it can reduce the blast radius of changes to the others.
- You pay only for the specific tools you use, which can suit a small or single-segment book.
This page compares general operating approaches, not any specific product or provider. Your experience depends on your own tools, data and processes. Published by Regalis.
Separate portals vs unified stakeholder portals — FAQ
Do trustees, owners and tenants all log into the same place?+
With a unified portal they each get their own login, but those logins open scoped views of the same underlying records rather than separate copies of the data. Role-based access controls what each group can see and do. With separate portals, each group logs into its own tool, and matching the data across them is a manual step.
Is a unified portal always the right choice?+
Not always. If one stakeholder group needs a specialist tool that a general platform cannot match, or you are mid-transition and not ready to consolidate, separate portals can be reasonable. The trade-off is duplicated data, repeated access management and extra reconciliation, which a unified approach is designed to avoid.