Documents and assets

Secure documents

Attach private files to customer and operational records.

How it works

Keep files private and attached to the work they support

Store private files against customer and operational records, with version history and workspace-scoped access. Customer sharing is deliberate and takes place through the authenticated portal.

01

What it covers

Use version history, workspace-scoped access, deliberate customer sharing and authenticated portal uploads.

02

In practice

Portal uploads and shared files follow the record’s access controls.

When to use it

Useful situations

  • Attach a private contract to a customer record.
  • Maintain a versioned operational file with controlled access.
  • Share a selected file through the authenticated portal.

A working path

How the work moves

  1. Attach

    Upload the document to the related operational or customer record.

  2. Manage

    Review version history and workspace-scoped access.

  3. Share

    Select customer sharing when a portal contact needs the file.

Illustrative scenario

signed proposal

A commercial owner uploads the signed proposal, keeps the current version on the contract, then shares it with the approved portal contact. The owner can replace a draft with the signed version while preserving the earlier version history, then choose whether the customer should receive the current file.

Before you start

What to check

  • Documents are private unless explicitly shared.
  • Malware scanning is not represented as live until the provider rollout is complete.

Questions about Secure documents

Useful details before you start.

All questions
Are documents public links?

No. Customer access requires authenticated portal access and a sharing decision.

Can we see versions?

Yes, version history is retained for supported document workflows.

Get started

See your customer work in one place.

Start with the core CRM for free, then add the tools your team needs.