What's new

An audit log you can filter and export

Workspace Admins see one timeline of the changes made in their organization and of what happened on its requests and documents. Each entry shows who did it, when, and the IP address it came from, or "System" for an automatic event.

• Filter by date range, by type ("Admin Actions" or "Request Activity"), by category, by a search, or by one request.
• Open any entry to see its details, such as the exact time and, for request activity, the browser it came from.
• Export what you see as a CSV file of up to 10,000 rows.

Entries never hold file names or document content, and they are never deleted.

Requested by, a Reference ID and plain file type choices

• Each request shows who on your team created it, or "API" when your system created it.
• Give a request your own Reference ID, such as an order number, of up to 255 characters. It appears in the Requests list, on the request, in the upload notification email and in the webhook.
• Choose the files a request accepts with plain choices: photos and images (PNG and JPG), PDF documents, Word documents and Excel spreadsheets. The upload page tells the recipient in plain words which files it accepts.

Upload notifications, recorded on the request

When a recipient finishes an upload, FileCourier emails the person who created the request and every other active member of your workspace, and records those emails on the request, with who was emailed. The recipient gets a confirmation email when the request has an email address.

Your logo on the Upload Complete page too

The logo your workspace uploads, on the upload page and the passcode screen since October 18, now also appears on the Upload Complete page, scaled to a set height on phones and computers. A logo sent with a request through the API takes its place, and with no logo the page shows the name of your project or brand.

The Reviewer role

A Reviewer can create requests (and send one again when its email or text message could not be sent), see requests and who opened their documents, and open documents. A Reviewer cannot cancel requests or delete documents, cannot change projects, the team, billing, retention, branding or the MFA policy, and does not see the audit log. Requests are cancelled through the API with a project's credentials, which a Reviewer cannot see.

Multi-factor sign-in, with a workspace policy

Named users can turn on multi-factor sign-in with an authenticator app, with recovery codes for a lost phone. A Workspace Admin can require it for everyone in the workspace; members then set it up when they next sign in. New workspaces start with the requirement off.

A passcode on upload links

A Workspace Admin can require a passcode for a project. Before the recipient sees the request, FileCourier sends a six digit code on the channel the request used: by email when the request went by email, or by email and text message, and by text message when it went by text message only. A code lasts 10 minutes and allows five tries.

Retention you control

A Workspace Admin sets how long uploaded documents are kept, from five minutes up to 72 hours, counted from upload. New workspaces start at 24 hours. About a minute after the period ends, FileCourier deletes each document, whatever the request's status and whether or not anyone opened it.

An access record for every document open

In the dashboard, documents open only for signed-in members of your workspace, and every open there is recorded with the person, the time and the IP address, on the request's Access record tab. The record is kept after the document is deleted.