Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Field staff versus office staff: different access needs for the same hosted app

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

The same hosted line-of-business application can serve office analysts and field operators, but the access journey should not be identical. Office staff may need multi-monitor native sessions, heavy printing, and stable LAN paths. Field staff often need narrow tasks, tolerant mobile networks, and clients that work on phones or tablets—when the app and publishing model actually support that.

Why it matters

Ops leads standardise one remote template and wonder why drivers abandon the iPad app. Role-based design reduces licence noise, shrinks support scope, and avoids forcing gateway/VPN choices that suit headquarters only. This is access-pattern design, not “RD Gateway vs site-to-site VPN” triage.

How it works

Microsoft describes users reaching session hosts via Remote Desktop clients on Windows, macOS, iOS, and Android or via a supported browser web client. RD Gateway enables encrypted access from public networks without mandating a VPN. Collections can scope specific apps for specific groups on the session host side.

Authorization at the gateway splits who may connect (CAP) from which resources (RAP) in documented event semantics. Field and office roles can therefore map to different published collections, gateway policies, or client instructions—even before conditional access rules at the identity layer.

The Remote Desktop web client does not support mobile devices; phones and tablets should use the native Remote Desktop apps for those platforms, piloted against your published resources.

Labelled example — office — inventory controller: Full desktop, dual monitors, host-visible label printer, native Windows client on wired LAN.

Labelled example — field — delivery driver: Single published RemoteApp for proof-of-delivery, Android client on LTE, training to save PDFs to hosted share—not local gallery.

What to choose and why

Write two role journey maps for your organisation:

Journey element Office typical Field typical
Client Native desktop Native mobile client (iOS/Android); browser only on supported desktop OS
Session shape Desktop or multi-app RemoteApp tile
Network Office LAN / stable home Cellular, short sessions
Peripherals Printers, scanners Camera/upload, minimal print
File custody Hosted share standard Avoid local-only saves

Align identity groups with those journeys so CAP/RAP and collection membership stay maintainable.

Risks and limits

Not every LOB UI fits phone screens; “field access” may mean a different module or offline process. No journey was lab-validated.

Sources

Related reading

Learning notes

  1. One hosted app can have multiple publish/client patterns by role.
  2. Field journeys should be shorter and task-scoped by default.
  3. Gateway roles separate people from resource targets—use that in design.
  4. Mobile success requires LOB UI fit and the native mobile client—not the web client.
  5. Journey maps expose hidden assumptions (printers, saves, MFA timing).