Skip to main content

Protect data and share the right document

Before sharing a record, export or document, identify the product, recipient and information actually needed. Operations access and CRM access remain separate.

Before you start​

Use your own account, the correct Operations organization or CRM workspace and the required permissions. Confirm who should receive the file. The same company name in both products does not prove data sharing.

Steps​

  1. Open the source record and check its context. After switching organizations or workspaces, read the information again before acting.
  2. For an export, select the useful scope and inspect the resulting file. List filters and export permission are separate controls; not everything in the workspace should necessarily leave it.
  3. For an adapted document, review the exact PDF revision before approval. Share that approved version with the intended recipient and check the sharing state.
  4. Keep response and confirmation links private. A link may permit a specific decision; do not include its secret part in screenshots or support requests.
  5. For an incorrect recipient, use available withdrawal or revocation actions and inform your responsible contact. Revoking the original share cannot recall a copy already downloaded.

Example and expected result​

Fictional example: Camille needs instructions for one site. The manager checks the document for that site and visit, approves its revision and shares that version. They do not send the full client file or all contacts. Successful preparation does not prove Camille received or read the document.

If something goes wrong​

For refused access, check role and scope; do not use a colleague’s account. Remove unnecessary contact details, passwords, sign-in codes and secret links from support requests. Archiving or hiding a record does not prove permanent deletion. Consult applicable service conditions with your responsible contact for retention periods; this guide states no unverified duration.

Continue​