HelpReportsShare a report
Reports · 4 min read · Fast

Share a report

Create a recipient-safe report link with sender context, access expectations, and tracking intact.

ReportsCURVEAdvisorFast
OutcomeA recipient-safe report link with the right context, sender label, and view tracking.
Best forAdvisor using CURVE with client-facing data
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 exact report you want to send and put it in Report mode so the recipient lands on the polished report, not the data workbench.
  2. Click Share. Wait for the dark share modal with the email field, Send button, and Copy share link button.
  3. To email it directly, type the recipient email into the field and click Send. Wait for the Sent confirmation before closing the modal.
  4. To use your own thread, click Copy share link, wait for the button to change to Link copied, then paste the link into the message you are sending.
  5. Open the shared link in a new tab and verify the report title, sender context, and visible pages are correct before telling the recipient to use it.
03

Mistakes to avoid

Sending a report before checking the exact Data, Split, or Report mode the recipient will open.

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 report?

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