Sharing & Collaboration · 4 min read · Fast

Share a Unit

Send share a unit safely, with the correct recipient access, sender context, and tracking expectations.

Sharing & CollaborationCURVESender,Fast
OutcomeA single-unit story the recipient can open without platform training.
Best forSender, recipient, or account owner
EffortFast · 4 min read
01

Fast read

Start from the exact surface

Use the left sidebar or direct page link named in the guide, then check the visible page title before touching filters, sends, downloads, or billing buttons.

Prove the recipient view

Open the final page, shared link, tracker link, embedded widget, or exported report in the same browser before treating the task as complete.

Capture support evidence

Copy the URL from the address bar, note the account email in Account Settings, take a screenshot, and include the last button you clicked.

02

Step-by-step

  1. Open the unit page from Buildings, Data, a report, or search, then verify the building name and unit label at the top of the page.
  2. Click the Share Unit button and wait for the dark modal with the email input and Copy share link option.
  3. Use Send when CURVE should email the page directly, or Copy share link when you want to paste the link into your own message.
  4. Open the shared unit link in a new tab and confirm the transaction chain, timeline, and building/unit label match the unit you meant to send.
  5. If the recipient needs broader platform access instead of one unit page, use an invite workflow rather than repeatedly sending unit links.
03

Mistakes to avoid

Using an invite when a one-artifact share link is the safer recipient experience.

Changing filters or modes without checking the final rendered surface.

Assuming a highlighted, shared, or pinned item changed source truth instead of presentation or access.

04

Frequently asked questions

What should I check first for share a unit?

Start with account, URL, selected mode, filters, building or unit, date range, and recipient context. Most confusion comes from looking at the right data through the wrong workflow state.

Does this change the underlying data?

Most controls change the view, filter, workflow state, access, or presentation layer. Source sale and unit records remain unchanged unless an admin data-sync or data-correction process explicitly updates them.

How do I know this is ready for a client?

Open the final surface the client will see and verify that the key evidence, action, label, or next step is visible without needing you to narrate it separately.

What should I send support if this still fails?

Send the account email, URL, building or unit, saved search or report name, timestamp, screenshot, and the exact action you took immediately before the issue appeared.

05

Related guides