Workspace switcher
One identity, multiple organisations. Switch in two clicks; the audit trail records which workspace each action belongs to. No accidental cross-posting.
Feature · Multi-org & trust
Run two organisations from one identity. Without their data touching.
Martin Masterumbe is the Director of Cyprus Constructions and the Super Admin of CTS. He signs in once and switches workspaces the way a finance lead switches fiscal years. One login. Two organisations. Zero leakage. Every action audited.
Roles · cross-organisationaudit logged
Active workspace
Cyprus Constructions
10 active projects · 9 seats
CTS · Ceyhun Tunalı & Sons
1 active project · 2 seats
One Director identity. Two organisations. Switching writes an audit row; nothing leaks across the boundary.
| User · Workspace | Sales | Approvals | Finance | Settings |
|---|---|---|---|---|
| Redif EkinciFounder · Super Admin · Cyprus Constructions | ✓ | ✓ | ✓ | ✓ |
| Martin MasterumbeDirector · Super Admin · CC + CTS | ✓ | ✓ | ✓ | ✓ |
| Anna · Sales leadSales lead · Cyprus Constructions | ✓ | ✓ | — | — |
| Sina · FinanceFinance · Cyprus Constructions | — | — | ✓ | — |
| CTS — OperationsMember · CTS | ✓ | — | — | — |
Organisations run today
2
Cyprus Constructions + CTS — by one Director
Cross-org data leaks
0
Enforced by workspace boundary, not a permission flag
Days to onboard a sister org
11
CTS · Carob Hill, Tatlısu · live in 11 days
Audit coverage
100%
Every action, every actor, every workspace
Role-based access
Roles are organisation-scoped. The Director role at Cyprus Constructions does not grant Director powers at CTS — even though it’s the same person. Permission lives with the workspace, not the user.
Immutable audit log
Every status change, approval, document upload, role assignment, and permission change writes to an append-only log. Exportable for legal, finance, and external auditors.
Roles · cross-organisationaudit logged
Active workspace
Cyprus Constructions
10 active projects · 9 seats
CTS · Ceyhun Tunalı & Sons
1 active project · 2 seats
One Director identity. Two organisations. Switching writes an audit row; nothing leaks across the boundary.
| User · Workspace | Sales | Approvals | Finance | Settings |
|---|---|---|---|---|
| Redif EkinciFounder · Super Admin · Cyprus Constructions | ✓ | ✓ | ✓ | ✓ |
| Martin MasterumbeDirector · Super Admin · CC + CTS | ✓ | ✓ | ✓ | ✓ |
| Anna · Sales leadSales lead · Cyprus Constructions | ✓ | ✓ | — | — |
| Sina · FinanceFinance · Cyprus Constructions | — | — | ✓ | — |
| CTS — OperationsMember · CTS | ✓ | — | — | — |
- Org switcher: Top-left. Two clicks to swap workspace.
- Scoped roles: Director here ≠ Director there.
- Audit row: Workspace + actor + action + timestamp.
The architecture behind the dual-org story
Inventory in one. Inventory in the other. Nothing leaks across.
CTS — Ceyhun Tunalı & Sons — is a Cyprus developer that operates parallel to Cyprus Constructions. The two brands share a Director. They do not share buyer pipelines, units, or finance. The platform had to make that easy without forcing two logins.
Martin signs in once. Inside, he sees two organisation cards — Cyprus Constructions and CTS — each with its own dashboard, its own projects, its own buyers, its own currency settings, and its own audit trail. Switching between them is the navigation primitive, not a configuration toggle.
When a new CTS project launches, the team configures it in the CTS workspace. No leakage of buyer or pricing data to the Cyprus Constructions side. The reverse holds in equal measure. Two organisations, one Director, zero cross-contamination.
A Director, two workspaces
One login. Switch. Act. Audit.
- 01MartinSigned in
Single identity · two organisation cards visible
- 02MartinSelected CTS
Workspace switched in two clicks · audit row written
- 03MartinApproved
A Carob Hill reservation cleared · scoped to CTS only
- 04MartinSwitched back
Cyprus Constructions workspace · Bahamas Homes pipeline visible
- 05AuditRecorded
Both actions logged with workspace boundary preserved
What teams actually get
Concrete operational outcomes — not abstract benefits.
- Related entities run from one identity without their pipelines touching
- Role permissions scoped to the workspace, not the user
- An audit log finance, legal, and external auditors all read the same way
- Onboarding a sister organisation measured in days, not quarters
- Workspace boundaries enforced by architecture, not a config flag
- Hosting region selectable per organisation (EU, GCC, NA, APAC)
Inside the feature
The real modules teams use day to day.
Each card maps to a live surface in the workspace. The names below are the names the product team uses internally.
Multi-organisation identity
One login, multiple organisations. Switch in two clicks; every workspace is its own tenancy with its own data, currencies, branding, and audit.
Roles & RBAC policies
Role design, policy assignment, user provisioning. Permissions live with the workspace, so the same person can carry different power in different orgs.
Audit, notifications, support
Immutable audit log per workspace, named-notification routing, and the support-ticket queue — every event with workspace, actor, and action.
“I run two organisations from the same identity. Cyprus Constructions and CTS share a Director — me — but they are not the same company, and their pipelines must not touch. The platform handles that cleanly. One login, two workspaces, zero leakage.”
Questions teams ask
What buyers want to know before they sign.
The questions we hear in the demo. If yours isn’t here, the demo itself is the fastest way to get a direct answer.
01Can two organisations under the same Director share a customer record?
No. The workspace boundary enforces full isolation of buyer records, units, and finance. If a customer relationship needs to exist in both orgs, two records exist — one per workspace — and the operator is conscious of which they’re acting in.
02What does the audit log capture, exactly?
Every status change, every approval, every role assignment, every permission change, every document upload — with workspace, actor, timestamp, prior state, and reason where required. Append-only. Exportable.
03Can each organisation choose its own hosting region?
Yes. The two organisations under the same Director can sit in different hosting regions if their data-residency needs require it — Cyprus Constructions in EU, a sister entity in GCC, for example.
04How does support work across organisations?
Support tickets are workspace-scoped. A ticket raised in Cyprus Constructions cannot reference data from CTS, and vice versa. The support team sees only what the requesting workspace exposes.
More inside the platform
Adjacent surfaces teams use alongside this one.
Sales workspace
From inquiry to reservation, in one view.
The pipeline, the approval chain, and the unit-level price book on a single workspace — so the sales floor and the manager are looking at the same deal at the same time.
See the featureInstallments
Off-plan reservations live or die on payment plans.
Build, template, and run installment plans across hundreds of buyers — with a pending queue finance actually opens, overdue alerts that mean something, and analytics that show the cohort shape before the month closes.
See the featureWant to see it on your own deal flow?
Book a 30-minute walkthrough.
We map your team, markets, and modules — and quote the per-seat range you can take to your finance lead.
Ready when your team is
Give every property deal a clear place to move forward.
Start with the core workspace, then add the client, finance, reporting, and governance modules your organization needs.