Administration
Roles and permissions in Virtual Desktop Infrastructure
Each role in Virtual Desktop Infrastructure: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Virtual Desktop Infrastructure 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 Virtual Desktop Infrastructure. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Citrix / Azure AVD as part of the managed service.
Roles
Desktop user
Loan officer, loan processor, underwriter, branch staff, operations staff. Uses the hosted desktop or published applications to work with customer information without storing it on their own device.
- Sees: The desktops and applications assigned to their user group; Their own files and settings inside the hosted session; Service notices about planned maintenance
- Does: Signs in through your identity provider with multi-factor authentication; Works in the hosted applications and stores files in approved locations; Logs off or resets their own stuck session; Raises support requests through your help desk
- Cannot: Copy, download or print outside what the data-transfer policy allows; Install software in the hosted desktop; See other users' sessions or files
- Approvals: Their access is approved by their manager and the service owner; nothing they do needs further approval.
- Notified about: Planned maintenance affecting their desktop, and changes to the applications they use.
Business manager
Lending manager, branch manager, operations manager. Decides which of their staff need which desktops and applications, and confirms it periodically.
- Sees: Their team's access to desktop pools and applications; Access requests they raised and their status; Access review lists for their team
- Does: Requests access for new staff and removal for leavers; Approves access requests for their team; Confirms or removes access during access reviews; Requests new applications for their team through the service owner
- Cannot: Approve access outside their own team; Approve changes to images or data-transfer policies; Grant exceptions to the data-transfer policy
- Approvals: Access they approve also needs the service owner's approval where your procedures require it.
- Notified about: Access requests waiting for them, access reviews due, and accounts on their team not used for a period your policy sets.
Service owner
IT manager, end-user computing manager, IT director. Owns the virtual desktop service at your institution and is Moraph's main point of contact.
- Sees: All desktop pools, images, users and open requests; Monitoring summaries, incidents and capacity; Change history and the monthly service review; Licence counts and renewals
- Does: Approves change requests to images, pools and applications; Approves access to desktop pools; Sets maintenance windows and capacity limits; Attends the monthly service review and agrees actions; Approves Moraph administrative access to your environment
- Cannot: Approve exceptions to the data-transfer policy without the security officer; Change audit logs; Approve a change they requested themselves where your procedures require a second approver
- Approvals: Approves changes and access; changes that affect data-transfer policy also need the security officer.
- Notified about: Change requests waiting for approval, incidents affecting users, vendor service notices, and licence renewals coming due.
Information security officer
Information security officer, CISO, IT risk manager. Decides how customer information may move in and out of hosted sessions, and checks that the environment matches the approved baseline.
- Sees: Data-transfer policies and exceptions by user group; Baseline reviews and deviations; Session and administrative logs; Security incidents involving the service
- Does: Approves data-transfer policies and each exception; Reviews baseline deviations and decides how they are resolved; Reviews administrative activity by Moraph and your own staff; Requests logs and evidence for audit or investigations
- Cannot: Apply changes to the environment directly; Edit or delete log entries; Approve an exception they requested themselves
- Approvals: Approves data-transfer policies, exceptions and security-relevant changes.
- Notified about: Exception requests, baseline deviations, security incidents and changes to administrative access.
Moraph service engineer
Moraph end-user computing engineer, operations engineer. Runs the platform for you: builds and patches images, monitors the service, responds to incidents and carries out approved changes.
- Sees: Platform configuration, monitoring and alerts; Change requests and incidents for your environment; Vendor service notices
- Does: Builds, tests and patches golden images; Triages alerts and resolves or escalates incidents; Carries out approved changes and records the evidence; Raises cases with Citrix or Microsoft when the vendor's service is involved; Prepares the monthly service review
- Cannot: Make a change that has not been approved, except emergency actions your contract allows, which are reported straight away; Grant themselves access to your environment; access is approved by your service owner; Open users' files or sessions without a recorded support reason and your agreement
- Approvals: All changes are approved by your service owner, and policy changes by your security officer.
- Notified about: Platform alerts, user-affecting incidents, approved changes ready to schedule and vendor notices.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews access, change and service records without being able to change anything.
- Sees: Access review results and access history; Change requests and their approvals; Baseline reviews and monthly service reports; Session and administrative logs within the granted scope
- Does: Reads and exports records within their scope, with each export logged; Requests further evidence through the service owner; Leaves review notes where your institution enables them
- Cannot: Change, approve or delete anything
- Approvals: Their access is approved by the service owner or security 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.
Help desk
IT help desk analyst, desktop support technician. Gives first-line support to your staff and passes platform issues to Moraph.
- Sees: Users, their assigned desktops and current session status; Open tickets and their status with Moraph; Known issues and planned maintenance
- Does: Resets or logs off stuck sessions; Raises access requests on behalf of managers; Logs and escalates platform issues to Moraph; Tells users about planned maintenance and known issues
- Cannot: Approve access or changes; Change images, pools or data-transfer policies; View the contents of a user's session
- Approvals: Requests they raise are approved by the manager, service owner or security officer as appropriate.
- Notified about: Incidents affecting users and updates on tickets they escalated.
Permissions at a glance
| Action | User | Manager | Service owner | Security | Moraph eng. | Auditor | Help desk |
|---|---|---|---|---|---|---|---|
| Use an assigned desktop or app | Full | Full | Full | Full | – | – | Full |
| Request access for a person | – | Own work | Full | – | – | – | Full |
| Approve access to a desktop pool | – | Approves | Approves | – | – | – | – |
| Reset or log off a session | Own work | – | Full | – | Full | – | Full |
| Raise a change request | – | Full | Full | Full | Full | – | Full |
| Approve image and pool changes | – | – | Approves | View | – | View | – |
| Approve data-transfer policy exceptions | – | – | View | Approves | – | View | – |
| Apply approved changes | – | – | – | – | Full | – | – |
| View monitoring and incidents | – | – | View | View | Full | – | View |
| View session and admin logs | – | – | View | View | View | View | – |
| Confirm access in reviews | – | Own work | 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 act only on approved change requests. Emergency actions allowed by your contract are reported to the service owner straight away and recorded like any other change.
- Roles follow groups in your identity provider, so joiners, movers and leavers are handled where you already manage them. Desktop pools and published applications can be limited by team, branch or business line.
- Data-transfer exceptions are approved by your security officer, never by the person asking for them, and each exception has a reason and a review date.
- Moraph's administrative access to your environment uses named accounts approved by your service owner, and every administrative action is logged. Auditors and examiners 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.