Collect files from someone outside Evolve

Open Secure Data Intake in the left rail and choose New request. Name the request, pick the managed folder the files should land in, add the recipients' email addresses, and choose Issue request. Each recipient gets a link that verifies their email and accepts the files.

The rail row appears only for people who administer intake. Its own description reads Issue secure upload links, monitor delivery, and route accepted files into a managed folder.

Issue a request

1. Choose Secure Data Intake, then New request. The dialog says Create a secure upload link for one or more named senders.
2. Type a Request name.
3. Choose the Destination managed folder. Folders belonging to a Space are grouped under Spaces.
4. Add Recipients, one email address per line. The help text says Enter one email address per line. Addresses are used only for identity matching and delivery.
5. Write Sender instructions. The sender sees them on the upload page.
6. Open Limits and handling if the defaults do not fit. It carries Per-file limit (GB), Total limit (GB), Maximum files, Concurrent uploads, Expires after (days), Purpose reference, Classification reference and Retention profile. The panel notes Any file format is accepted under the returned policy. Unrecognized formats use store-only handling.
7. Choose Issue request. It reads Issuing… while it works.

What the sender does

The sender opens the link and sees Secure Data Intake with your instructions and the request limits. They enter their Email address under Verify your email, which explains Use the email address that received this request. Evolve will send a one-time code., then choose Continue securely.

They then choose files or a folder and start the upload. The page describes itself: Choose files or a folder. Any file type allowed by the request policy can be transferred. Uploads can be paused and resumed, and the receipt page says You can close this page. The safe receipt below is authoritative.

The footer states what happens next: Files are admitted by request policy, scanned, validated, and delivered only to the designated managed folder.

Track a request

The list shows Request, State, Expires, Submissions and Attention. Open a row for its details, its policy and its submissions.

Invitations holds one row per recipient. Add or reissue issues a new link for an address; the help text warns Reissuing creates a fresh link and invalidates the previous one. Delivery status does not control access. Revoke withdraws an invitation and ends its sessions.

On the request itself, Expire stops new uploads and Revoke ends every active sender session. Both ask you to confirm.

Submissions lists each file with File, State and Size, and counts the uploaded files against the declared total for each submission.

When something needs attention

• Scanning needs review holds the affected files. The note says the affected files stay isolated and cannot be delivered, and gives the support reference to quote when escalating.
• Destination needs attention means the delivery could not be bound. Enter the Managed folder ID, optionally a Folder ID (optional), and choose Rebind destination.
• Notification delivery needs attention. Reissue if the recipient did not receive a usable link. means the email may not have arrived. Use Add or reissue.

If it did not work

• Destination managed folders could not be loaded. means the folder picker failed. Reload the page.
• The intake request could not be issued. means nothing was created. Try again.
• Intake requests could not be refreshed. Existing results remain available. means the list is stale, not empty.
• A sender who reports This request is not available holds a revoked or expired link. Issue a fresh one.
• Administering intake needs the intake capability on your role. If the rail row is absent, ask an Account administrator.