Share the property records
each client is authorized to see.

Plan a client experience around the relationship, with only the records, fields and files your firm chooses to share.

Book a guided demo

Preview the records selected for one tenant relationship.

This walkthrough uses fictional records. Follow the pointer or try each local action.

Illustration only · No live actions
Harbor CommercialClient experience preview
Fictional workspace
Harbor CenterConnected property recordFictional data

Connect Jordan’s access scope to the tenant relationship

Illustrative tenant access · setup dependent

1 / 4

Jordan Lee

Harbor Design Group

Tenant · Suite 100
PropertyHarbor Center
RelationshipTenant
Record scopeSuite 100
Default accessNothing shared

External access requires an explicitly authorized client relationship and remains separate from workforce access.

Share the record, fields and files deliberately

Scope illustration · no live client access

2 / 4
Harbor Center · Suite 100 details

Specific record · Read only

Ready
Executed lease · Reviewed version

Specific shared document

Ready
Commission detailsNot shared
Other tenant recordsNot shared
Internal property notesNot shared

Record, field and file scope are different decisions. Internal information stays outside the illustrated shared view.

Preview the Suite 100 records selected for the tenant

Client portal illustration · not active access

3 / 4
Harbor Center
Tenant view

Welcome, Harbor Design Group.

Review the records shared for Suite 100.

Suite 100 · Executed leaseShared reviewed version
Your suite100
Your relationshipTenant

The client preview shows only the selected property relationship and reviewed file.

Keep other tenants’ records outside the shared view

Default-deny relationship scope

4 / 4
Harbor Center
Tenant view

Welcome, Harbor Design Group.

Review the records shared for Suite 100.

Suite 100 · Executed leaseShared reviewed version
Your suite100
Your relationshipTenant
Other tenant records are not shared.

Access stays within the authorized relationship.

Client portal availability depends on deployment setup and authorization. This walkthrough creates no external account or access.

Choose a step or play the walkthrough.

The complete illustrated sequence remains readable when motion is unavailable. The examples use fictional records and perform no live actions.

Preview the records selected
for the tenant’s relationship.

Harbor Design Group occupies Suite 100. The client view could show shared property details, the selected lease and the firm’s approved point of contact. It should not expose Signal Supply’s records, internal commission information or staff-only documents simply because those records belong to the same building.

The staff preview lets the team inspect the intended perspective before inviting anyone. That makes the sharing decision concrete: which relationship is active, which record is relevant and which fields or files are permitted? A preview is a way to check that boundary; it is not a signed-in client session.

Harbor CommercialFictional product example

Preview the view before sharing it

Viewing asHarbor Design Group · Tenant
Read-only staff preview

Review your shared Suite 100 records.

Suite 100 · Shared property context

Executed leaseThe version selected for this relationship
Shared
Property contactYour firm’s approved point of contact
Shared
Maintenance areaVisibility depends on deployment setup
Preview

A staff preview is not an invitation, an active client session or payment activation.

This workflow uses fictional records and performs no live actions.

Set client access
for the specific relationship and records.

External access is different from workforce access. A tenant, owner or other client principal needs the relationship and scope that fits their role in the work. Access should reflect the effective relationship and the records it permits, rather than copying a staff role or opening an entire property workspace.

The same care applies to shared documents. Select the appropriate file and version, then inspect the client-facing view. The fact that a staff member can open a document does not mean it belongs in a client’s portal. Changes in a relationship should be treated as access changes, not merely edited contact details.

Configure each client area
before authorizing access.

Depending on the deployment, the client experience may include selected properties, deal status, shared documents, messages, invoices and maintenance areas. Each area needs the right configuration and release status. Start with the information the client needs most, then test the actual perspective before widening the experience.

Payment collection needs its own account setup, authorization and release checks. An invoice or ACH preview does not activate it. AI never makes payments or refunds; a browser return is not proof of payment.

Harbor Commercial
Fictional product example

Client preview for Harbor Design Group

Client portal preview · Harbor Design Group

Read-only preview
Preview only. No client is signed in.Scoped access

Welcome to Harbor Center.

View the property details and documents your firm has shared.

PropertyHarbor Center · Suite 100
Shared documentExecuted lease · reviewed version
RelationshipTenant · View only
Other tenants’ recordsNot shared

Access follows the relationship, the record and the fields your team authorizes.

Choose what to share.
Check who can see it.

Client access is a planned release. Give the responsible people a concrete preview and keep invitation, communication and payment decisions distinct.

  1. Relationship owner

    Confirm the client’s current connection to the relevant property or deal and identify the information the client needs.

  2. Access reviewer

    Inspect the scoped preview, document versions and field visibility, including what must remain private.

  3. Authorized administrator

    Complete the deployment setup and invitation checks before opening access. Enable other consequential areas only through their own release process.

Check the review and setup requirements.

Check how review, access and deployment setup affect this capability.

Is the client portal active for every deployment?

No. Portal visibility, messaging, maintenance areas and payment options depend on setup and rollout. The site presents a scoped preview, not universal activation.

Can a client see the whole property workspace?

The intended view follows the effective relationship and permitted records, fields and files. It should not grant workforce access or disclose other parties’ information.

Does an invoice view mean online payment is enabled?

No. Payment account setup, authorization and release checks are separate. A screen does not prove collection is active or that money has been received.

Bring a workflow
to your guided demo.

Choose a renewal, listing or maintenance request. We’ll walk through the records, responsibilities and review steps in Crezoa.

Book a guided demo