Skip to content

Getting started

Getting started with Secure File Transfer

What Secure File Transfer is for, who uses it, what you need before you start, and your first steps.

Applies to Secure File Transfer as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

Moraph resells, implements and runs Kiteworks so your clients can upload tax returns, statements and other sensitive documents through an encrypted upload link or portal rather than ordinary email. Kiteworks controls who can see each file, how long it is kept and every download, and Moraph configures it to your retention and data-handling policies. Moraph runs the service day to day, while your firm decides who has access and how long documents are kept.

What it is for

Wealth, trust, tax and lending teams still receive tax returns, bank statements and identity documents as email attachments. Those files sit in inboxes indefinitely, get forwarded, and leave no record of who opened them. Consumer file-sharing links are hard to control and harder to evidence. When a client asks how their documents are protected, or an examiner asks how customer information sent by email is safeguarded, the honest answer is often that it is not controlled.

  • Clients email tax returns and statements as ordinary attachments
  • Documents stay in inboxes and personal folders long after they are needed
  • There is no record of who opened or forwarded a file
  • Staff use consumer file-sharing tools the firm does not control

Who uses it

  • Wealth management, trust and private banking teams collecting client documents
  • Tax and accounting groups that receive tax returns and supporting records
  • Lending teams that collect statements and tax documents from borrowers
  • Compliance and information security officers responsible for customer information
  • IT teams that want the platform run for them

Before you start

  • Your organization uses Secure File Transfer as a managed platform from Moraph, under an agreement that covers it.
  • Licences for Kiteworks, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for Secure File Transfer with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.