Audit a sensitive file delivery

A delivery audit joins configuration and observed activity. It cannot recall copies already downloaded.

Before you start

• Use the current released client or web app and sign in to the intended account.
• Select the correct workspace and use non-confidential test data.
• Record the current setting or result before changing it.
• Keep passwords, API keys, recovery keys and private links out of screenshots and support messages.

Steps: audit a sensitive file delivery

1. Identify the exact share URL or link row.
2. Review password, recipient, expiry and download settings.
3. Open link activity and analytics.
4. Compare expected recipient events with recorded activity.
5. Revoke when the delivery should end.
6. Record the nonsecret outcome in the appropriate private system.

Expected result

The audit a sensitive file delivery workflow completes for the test item and its result remains visible after a refresh or reconnect.

Limits and important details

• Available controls depend on the current client version, plan, role and workspace policy.
• A successful connection does not grant permissions beyond its credential and workspace boundary.
• Verify important results with a harmless test before relying on the workflow.

Troubleshooting

The expected control is missing. Confirm the current client, active workspace and role, then check the relevant settings page.

The operation is rejected. Read the exact error and compare credentials, permissions, quota and workspace policy.

The result is still unclear. Repeat with one small test item and contact private support with the time, client version and nonsecret error.

Related guides

• Read link activity
• Use named recipients
• Revoke a link