Administration
Roles and permissions in Secure File Transfer
Each role in Secure File Transfer: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Secure File Transfer as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Secure File Transfer. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Kiteworks as part of the managed service.
Roles
Client or external recipient
Client, borrower, trust beneficiary, outside accountant or attorney. Sends documents to your firm and receives documents from it through a secure link instead of email.
- Sees: The upload request or files shared with them; Your firm's branded upload page; Files they uploaded, where your policy allows
- Does: Verifies their identity as your policy requires; Uploads requested documents; Opens or downloads files shared with them before they expire
- Cannot: See other clients' folders or files; Open a shared file after it expires or is withdrawn; Share files onward through Kiteworks
- Approvals: None; they act on requests and shares sent by your staff.
- Notified about: Upload requests and files shared with them, and expiry reminders where enabled.
Staff member
Relationship manager, tax preparer, trust officer, loan processor, client service associate. Collects and sends client documents securely for the clients they serve.
- Sees: Client folders they have been given access to; Upload requests and shares they created, with their status; Activity on files they shared
- Does: Sends upload requests to clients; Receives, opens and files uploaded documents; Sends files to clients and outside advisers with expiry and access limits; Withdraws a share sent in error
- Cannot: Open client folders they have not been given access to; Change retention periods or delete files under retention or legal hold; Turn off recipient verification or extend expiry beyond policy
- Approvals: Shares outside the limits your policy sets need the compliance officer's approval.
- Notified about: Documents uploaded in response to their requests, and shares about to expire.
Team manager
Wealth team lead, tax practice manager, lending operations manager. Decides which staff can see which client folders, and confirms it periodically.
- Sees: Their team's client folders and who can access each one; Their team's sharing activity; Access review lists for their team
- Does: Grants and removes staff access to their team's client folders; Reassigns folders when staff move or leave; Confirms or removes access during access reviews; Requests changes to folder templates through the service owner
- Cannot: Grant access to folders outside their team; Change retention or sharing policies; Delete activity logs
- Approvals: Access they grant is recorded and reviewed in periodic access reviews.
- Notified about: Access reviews due, staff leaving their team, and unusual sharing activity on their team's folders.
Service owner
IT manager, IT director, operations technology lead. Owns the service at your firm and is Moraph's main point of contact.
- Sees: Platform configuration, users and folder structure; Monitoring summaries, incidents and changes; Licence use and the monthly service review
- Does: Approves change requests to configuration, integrations and branding; Approves maintenance windows; Manages licence counts and renewals with Moraph; Attends the monthly service review and agrees actions; Approves Moraph administrative access
- Cannot: Change retention or sharing policies without the compliance officer; Open client files unless also granted folder access; Edit or delete activity logs
- Approvals: Approves changes; changes to retention or sharing policy also need the compliance officer.
- Notified about: Change requests waiting for approval, incidents, licence limits approaching and vendor service notices.
Compliance officer
Chief compliance officer, information security officer, privacy officer, records manager. Decides how long documents are kept, how they may be shared, and checks that policy is followed.
- Sees: Retention, sharing and verification policies; Activity logs across all folders; Legal holds and retention exceptions; Security alerts involving the service
- Does: Approves retention periods and sharing policies; Places and releases legal holds; Approves sharing exceptions; Reviews activity and exports logs for audit or investigation; Approves security-relevant configuration changes
- Cannot: Edit or delete activity logs; Approve an exception they requested themselves; Apply configuration changes directly
- Approvals: Approves retention, sharing and verification policies, exceptions and legal holds.
- Notified about: Exception requests, files flagged by scanning, unusual download activity and changes to administrative access.
Moraph service engineer
Moraph platform engineer, operations engineer. Runs Kiteworks for you: configures it, monitors it, applies updates and carries out approved changes.
- Sees: Platform configuration, health and security alerts; Change requests and incidents for your environment; Vendor service notices
- Does: Configures folder templates, policies and integrations as approved; Monitors health and triages alerts; Applies platform updates after testing; Raises cases with Kiteworks when the vendor's product is involved; Prepares the monthly service review
- Cannot: Open client folders or files without a recorded support reason and your approval; Change retention or sharing policies without approval; Grant themselves access; administrative access is approved by your service owner
- Approvals: Changes are approved by your service owner, and policy changes by your compliance officer.
- Notified about: Platform alerts, incidents, approved changes ready to schedule and vendor notices.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews policies, access and activity records without being able to change anything or open client files.
- Sees: Retention and sharing policies with their approvals; Access review results; Activity logs within the granted scope; Change history and service reports
- Does: Reads and exports records within their scope, with each export logged; Requests further evidence through the compliance officer; Leaves review notes where your firm enables them
- Cannot: Open client files unless your firm grants it specifically; Change, approve or delete anything
- Approvals: Their access is approved by the compliance officer, with a scope and an end date.
- Notified about: Nothing by default; access granted and expiring is confirmed to the person who approved it.
Permissions at a glance
| Action | Client | Staff | Team manager | Service owner | Compliance | Moraph eng. | Auditor |
|---|---|---|---|---|---|---|---|
| Upload requested documents | Own work | Full | Full | – | – | – | – |
| Send upload requests to clients | – | Own work | Full | – | – | – | – |
| Open files in client folders | Own work | Own work | Own work | – | View | – | – |
| Share files outside the firm | – | Own work | Own work | – | – | – | – |
| Approve sharing exceptions | – | – | – | – | Approves | – | View |
| Grant staff access to client folders | – | – | Own work | Full | – | – | – |
| Set retention and sharing policy | – | – | – | View | Approves | – | View |
| Place or release a legal hold | – | – | – | – | Full | – | View |
| Approve configuration changes | – | – | – | Approves | Approves | – | View |
| Apply approved changes | – | – | – | – | – | Full | – |
| View activity logs | – | Own work | Own work | View | Full | View | View |
| Approve Moraph admin access | – | – | – | Approves | View | – | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Moraph engineers manage the platform but do not open client folders or files. Where support needs it, access is requested with a reason, approved by your firm and logged.
- Client folder access follows teams: a team manager grants their own staff access, and access reviews ask them to confirm it periodically.
- Retention, sharing and verification policies are approved by your compliance officer, and exceptions are approved by someone other than the person asking for them.
- Staff sign in through your identity provider, and roles can follow its groups. External recipients verify their identity for each request or share, and auditors get temporary read-only access with a scope and an end date.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.