Data separation

Customer-safe visibility and business-only records

SamePage separates customer-facing project views from business-side operational records. That matters because the customer portal, partner coordination tools, Scope of Works flows, materials ledger and property history all contain different classes of information with different audiences and different legal risk.

Last updated 5 April 2026

Customer portal

Customers see customer-safe project status, messages, approvals, booking windows and agreed financial summaries relevant to their own job.

Business-only data

Internal pricing, margin, supplier cost, internal notes, staffing records and conduct flags stay outside the customer portal.

Partner sharing

Partner trade visibility is permission-based. Nothing is shared with another company until the relevant linking or collaboration step is accepted.

Property history

Property history records are structured for future works, but visibility is still controlled by role, consent and operational need.

What customers can normally see

Their own project status, stage progression and customer-safe appointment windows.
Messages, replies, customer requests, snag items, revisit proposals and sign-off requests relevant to their project.
Scope of Works summaries, approved variation summaries and customer-visible totals or status updates.
Property and access details they supplied, subject to role-based controls.

What customers do not see

Internal job costing, margin, supplier prices, markup logic or internal commercial commentary.
Detailed staff schedules, personal contact details, rota patterns, route traces or internal attendance controls unless deliberately exposed as a high-level customer status.
Internal risk flags, conduct notes, moderation markers, supplier negotiations or partner-company commercial arrangements.
Detailed materials ledger postings unless and until a business chooses to convert relevant items into customer-facing quote, variation or invoice detail.

How partner and multi-trade coordination is handled

SamePage supports consent-based partner linking, multi-trade sequencing and project collaboration. The platform is designed so that companies can share only the coordination layer they need, such as timeline dependencies, selected variation comments or limited scheduling windows.

Each business remains responsible for deciding what is appropriate to share, whether consent exists, and whether any customer confidentiality, contract or regulatory restriction applies before a document, photo, schedule or technical instruction is shared with another trade.

Property history and materials ledger records

Property history helps future jobs by storing a structured record of past scope, route changes, photos, handover detail and variation context. It is a project record, not a public property register, title record or independent survey report.

The materials ledger is an operational record of stock purchases, issues, returns and adjustments. It supports job costing and invoice preparation but is not, by itself, a customer approval, final invoice or proof that a customer accepted the underlying work or charge.

Access controls and practical limits

SamePage applies role, route and product-surface controls intended to keep internal data out of customer views. No software security measure is infallible, so users must also protect their credentials, devices and sharing practices.

If you think data has been misdirected, exposed to the wrong party or shared without the right authority, contact SamePage immediately through the legal contact route so the issue can be investigated and contained.