Skip to content

Administration

Roles and permissions in Asset Tracking

Each role in Asset Tracking: what it sees, does and cannot do, its approvals, and a permissions matrix.

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

Last reviewed 6 min readReport a problem
On this page
  1. Roles
  2. Clinical engineering manager
  3. Nurse or unit manager
  4. Equipment distribution lead
  5. IT network administrator
  6. Moraph RTLS engineer
  7. Moraph service manager
  8. Auditor or surveyor (read-only)
  9. Permissions at a glance
  10. How access is controlled

Who can see and do what in Asset Tracking. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Securitas Healthcare / AeroScout as part of the managed service.

Roles

Clinical engineering manager

Director of clinical engineering, biomedical engineering manager, HTM manager. Owns the tracking service for the hospital and decides which equipment is tracked, how it is managed and which changes are made.

  • Sees: All tracked equipment, its location, status and utilization; Maintenance and recall locating results, including devices not found; Tag health, change history and service reports; Issues Moraph has escalated, with recommendations
  • Does: Approves the configuration baseline and changes to it; Decides which device types are tagged and how they are registered; Runs maintenance and recall searches and assigns follow-up; Approves zone alerts and who receives them; Attends the monthly service review and agrees actions; Requests evidence for surveys and audits
  • Cannot: Approve a change they requested themselves, where a second approver is named; Edit or delete the change history
  • Approvals: Approves configuration, zone, alert and par level changes; changes they request themselves are approved by a second named approver.
  • Notified about: Changes waiting for approval, escalated issues, devices on a recall list that cannot be located, and tag health problems that need a decision.

Nurse or unit manager

Nurse manager, charge nurse, unit director, department supervisor. Makes sure the unit has the equipment it needs and that staff can find it.

  • Sees: Equipment on and near their unit, with its status; Their unit's par levels and current counts; Utilization reports for their unit
  • Does: Searches for equipment and directs staff to it; Marks equipment as needing cleaning or repair; Requests changes to par levels or zones for the unit; Reports equipment that is shown in the wrong place
  • Cannot: Change maps, zones, alerts or par levels directly; Register or remove tags
  • Approvals: Par level and zone changes they request are approved by the clinical engineering manager, with central distribution consulted.
  • Notified about: Par level shortfalls on their unit, where your configuration enables them, and the outcome of their requests.

Equipment distribution lead

Central equipment distribution supervisor, supply chain coordinator, transport lead. Moves equipment around the hospital so each unit stays at its par level and devices go back for cleaning and maintenance.

  • Sees: Par levels and counts across all units and storage areas; Equipment status, including devices waiting for cleaning; Utilization by device type and area
  • Does: Works the par level shortfall and surplus lists; Collects equipment for cleaning and returns it to service; Updates equipment status as devices move through processing; Proposes par level changes based on use
  • Cannot: Approve par level changes; Change maps, zones or alert routing
  • Approvals: Par level changes they propose are approved by the clinical engineering manager.
  • Notified about: Shortfalls and surpluses against par, and equipment marked as needing cleaning.

IT network administrator

Wireless network engineer, network administrator, infrastructure manager. Keeps the Wi-Fi network the tags rely on in good order and coordinates network changes that could affect location.

  • Sees: Location system health and accuracy test results; Changes planned to the tracking system that involve the network; Issues Moraph has traced to the wireless network
  • Does: Provides network access and settings the AeroScout system needs; Notifies Moraph of planned access point and network changes; Works network issues Moraph escalates; Approves network-related parts of a change
  • Cannot: Change tracking maps, zones, alerts or equipment records; Approve changes to how equipment is managed
  • Approvals: Approves the network parts of changes; the clinical engineering manager approves the rest.
  • Notified about: Location accuracy problems traced to the network and changes that need network work.

Moraph RTLS engineer

Moraph RTLS engineer, Moraph managed platform engineer. Builds and maintains the AeroScout configuration for the hospital and keeps tags, maps and zones working.

  • Sees: AeroScout configuration, maps, zones, alerts and tag records; System health, tag battery and reporting status; Approved change requests and the configuration baseline
  • Does: Applies approved changes to maps, zones, par levels and alerts; Registers, replaces and retires tags; Runs location accuracy tests and records the results; Triages system issues and escalates those that need a decision; Plans configuration work needed for AeroScout software updates
  • Cannot: Apply a change that has not been approved, except under the agreed emergency procedure; Approve their own changes; Decide which equipment is tracked or how it is managed
  • Approvals: Every change they apply is approved in advance by your named approver, or reported straight away when made under the emergency procedure.
  • Notified about: System health alerts, tags that stop reporting, and approved changes ready to apply.

Moraph service manager

Moraph service manager, Moraph customer success lead. Runs the service relationship, tracks requests and issues and reports on how the service is performing.

  • Sees: Requests, issues and changes and their status; Service reports, tag health and utilization summaries; Open actions from earlier service reviews
  • Does: Prepares and chairs the monthly service review; Tracks requests and escalations through to closure; Coordinates with the vendor on platform defects and service notices; Prepares evidence packs your team requests
  • Cannot: Change the AeroScout configuration; Approve changes on your behalf
  • Approvals: None; their reports and minutes are accepted by your clinical engineering manager.
  • Notified about: Escalations, overdue requests and vendor service notices affecting you.

Auditor or surveyor (read-only)

Internal auditor, compliance officer, accreditation surveyor (under temporary access). Reviews equipment records, changes and service evidence without being able to change anything.

  • Sees: Equipment records and status within the scope granted; Change history and approvals; Service reports and evidence packs
  • Does: Reads records and reports within their scope; Exports evidence they have been given access to, with each export logged
  • Cannot: Change, approve or delete anything
  • Approvals: Their access is approved by the clinical engineering manager, with a scope and an end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionClin. eng.Unit managerDistributionNetwork adminMoraph eng.Moraph serviceAuditor
Search for and locate equipmentFullOwn workFull–Full–View
Update equipment statusFullOwn workFull–Full––
Request a configuration changeFullOwn workOwn workOwn work–––
Apply a configuration changeApproves–––Full––
Change par levelsApproves–––Full––
Change zones and alert routingApproves–––Full––
Register, replace or retire tagsApproves–––Full––
Run maintenance and recall searchesFull–View–Full–View
Approve network-related changesView––ApprovesView––
Grant access to the tracking systemApproves–––Full––
View change history and service reportsView––ViewViewViewView

"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 apply changes; your hospital approves them. Nobody approves a change they requested themselves when a second approver is named.
  • Moraph staff use named, individual accounts in AeroScout with only the administrative rights the service needs. There are no shared administrator accounts.
  • Roles are agreed during implementation and can be limited by building, unit or department, so a unit manager sees the equipment that matters to their unit.
  • Every change is recorded with its request and approval in Moraph's change record. Auditors and surveyors get read-only evidence with a defined scope and end date.

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.