Administration
Roles and permissions in Cloud Content
Each role in Cloud Content: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Cloud Content 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 Cloud Content. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Box for Healthcare as part of the managed service.
Roles
Service owner
IT director, infrastructure manager, collaboration services lead. Owns the Box service for your organization and decides how it is configured and supported.
- Sees: Enterprise configuration and its version history; Usage, storage and licence reports; Open requests and incidents; Monthly service reports
- Does: Approves configuration changes; Approves the folder structure and who may create top-level areas; Reviews the monthly service report with Moraph; Agrees the support runbook and escalation routes; Approves licence changes
- Cannot: Apply configuration changes directly; Moraph applies approved changes; Open content in other people's folders by virtue of this role
- Approvals: Approves configuration changes; changes affecting sharing or classification also need the privacy officer.
- Notified about: Changes waiting for approval, service notices from Box and escalated incidents.
Privacy officer
HIPAA privacy officer, chief privacy officer, research compliance officer. Decides how content that may contain PHI is classified and shared, and whether events are reportable breaches.
- Sees: Sharing rules, classification labels and exceptions; Outside collaborator lists by folder; Security alerts escalated as possibly involving PHI; Legal holds in place
- Does: Sets sharing and classification rules; Approves or declines exceptions to sharing rules; Reviews escalated events and records breach determinations; Asks for legal holds with your legal team; Authorizes access to content for an investigation
- Cannot: Apply configuration changes directly; Change retention periods set by the records manager
- Approvals: Approves sharing exceptions and any change to sharing or classification rules; their own exception requests need a second approver you name.
- Notified about: Sharing exceptions requested, events escalated as possibly involving PHI, and holds placed or released.
Records manager
Records manager, health information management director, legal operations lead. Decides how long content is kept and makes sure retention and holds are applied as decided.
- Sees: Retention policies and the folders they apply to; Legal holds and their scope; Content approaching the end of retention
- Does: Sets retention periods by content type or folder; Requests retention policy changes; Works with legal to scope holds; Reviews disposition of content at the end of retention
- Cannot: Configure Box directly; Release a legal hold without your legal team's decision
- Approvals: Retention changes follow your records policy; Moraph applies them only on the records manager's written request.
- Notified about: Content reaching the end of retention and changes to holds.
Folder owner
Department manager, principal investigator, research coordinator, policy lead. Looks after a department or project area: who has access, what is shared and with whom.
- Sees: Their own folders, collaborators and shared links; Outside collaborator review lists for their folders; Activity on their folders
- Does: Invites colleagues and approved outside collaborators within the sharing rules; Removes collaborators when they no longer need access; Confirms access in periodic reviews; Restores their own deleted files within the recovery period; Requests exceptions and new folders through the service desk
- Cannot: Share outside the rules for the folder's classification without an approved exception; Change retention or holds on their content; Access areas they do not own or collaborate on
- Approvals: Exceptions to sharing rules are approved by the privacy officer.
- Notified about: Access reviews due, sharing exceptions decided and alerts about their folders.
Moraph Box administrator
Moraph collaboration platform engineer, Box administrator. Configures and administers Box so it reflects your decisions.
- Sees: Enterprise settings, users, groups and folder structure; Admin console reports and event logs; Box release notes and service notices
- Does: Configures settings, sharing rules, labels, retention and holds as approved; Manages users, groups and top-level folders; Plans and runs migrations; Applies approved changes and records each version; Raises platform issues with Box support
- Cannot: Open file content without your explicit authorization; Apply a configuration change without approval; Place or release a legal hold on its own decision
- Approvals: Every configuration change is approved by your service owner, and sharing or classification changes also by your privacy officer.
- Notified about: Approved changes ready to apply, migration issues and Box service notices.
Moraph support analyst
Moraph service desk analyst, security operations analyst. Handles day-to-day requests and reviews security alerts under the agreed runbook.
- Sees: Service desk requests and their history; Security alerts and the activity behind them; File and folder names, but not content
- Does: Resolves access, sync and sharing questions; Restores deleted files and earlier versions on request; Reviews unusual activity alerts and contacts the folder owner; Suspends a user's access under the runbook when activity looks malicious; Escalates events that may involve PHI to your privacy officer
- Cannot: Change configuration; Open file content; Make breach determinations
- Approvals: Actions beyond the runbook, such as removing a collaborator from a research folder, need the folder owner's or service owner's approval.
- Notified about: New requests, security alerts and replies to their escalations.
Auditor (read-only)
Internal auditor, external auditor, compliance reviewer. Reviews configuration, access and activity without being able to change anything.
- Sees: Configuration and change history; Access review results and outside collaborator lists; Activity reports and the audit trail within the scope granted
- Does: Searches and reads records within their scope; Exports reports they have been given access to, with each export logged
- Cannot: Change, approve or delete anything; Open file content
- Approvals: Their access is approved by the service owner, 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 | Service owner | Privacy | Records mgr | Folder owner | Moraph admin | Moraph support | Auditor |
|---|---|---|---|---|---|---|---|
| Propose a configuration change | Full | Full | Full | Full | Full | Full | – |
| Approve a configuration change | Approves | Approves | – | – | – | – | – |
| Apply configuration changes | – | – | – | – | Full | – | – |
| Create top-level folders | Approves | – | – | – | Full | – | – |
| Invite collaborators | – | – | – | Own work | – | – | – |
| Approve a sharing exception | – | Approves | – | – | – | – | – |
| Set retention periods | View | View | Full | – | – | – | View |
| Place or release a legal hold | – | Approves | View | – | Full | – | – |
| Restore deleted content | – | – | – | Own work | Full | Full | – |
| Review security alerts | View | View | – | Own work | Full | Full | – |
| Manage users and groups | Approves | – | – | – | Full | – | – |
| View audit trail | View | View | View | Own work | View | 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 administers Box without reading your content: Moraph staff see file and folder names and activity, and open content only with your explicit authorization, which is logged.
- Folder owners in your organization control everyday access to their areas, within the sharing rules your privacy officer sets; Moraph does not grant access to a folder without its owner or your service owner.
- Nobody approves their own change or exception. Configuration changes are approved by your service owner, and sharing or classification changes also by your privacy officer.
- Access to Box follows your identity provider's groups, and access and outside collaborator reviews run on the cycle you set. 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.