Administration
Roles and permissions in Visitor Management
Each role in Visitor Management: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Visitor Management 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 Visitor Management. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Envoy as part of the managed service.
Roles
Security director
Director of security, public safety manager, emergency management lead. Owns who may enter and on what terms, and uses visit records to manage incidents and risk.
- Sees: All sites, entrances and visit records; The watchlist and alerts raised against it; The configuration baseline and its change history
- Does: Approves the configuration baseline and changes to it; Decides who is added to or removed from the watchlist; Decides how watchlist matches are handled at the desk; Searches and exports visit records for incidents and audits; Chairs the monthly service review with Moraph
- Cannot: Apply configuration changes in the platform directly; Approve a change they requested themselves when a second approver is named
- Approvals: Approves the baseline, watchlist rules and changes to them; their own requests go to a named second approver.
- Notified about: Watchlist matches, changes awaiting approval, and platform incidents that affect entrances.
Front desk or security officer
Security officer, information desk staff, lobby ambassador. Signs visitors in at the entrance and applies the screening and watchlist rules.
- Sees: Expected and signed-in visitors at their entrance; Screening outcomes for visitors they sign in; Watchlist alerts for visitors at their entrance
- Does: Signs visitors in and prints badges; Captures photos and ID where policy requires; Handles a failed screening under the agreed procedure; Calls security leadership on a watchlist match; Signs out visitors and checks end-of-day lists
- Cannot: Change screening questions or watchlist entries; Search visit records outside their site; Override a screening or watchlist outcome without the procedure the security director set
- Approvals: Overrides of screening or watchlist outcomes need security leadership approval as your procedure sets.
- Notified about: Watchlist alerts and failed screenings at their entrance, and expected arrivals.
Host
Staff member, department manager, supply chain or facilities coordinator. Invites the guests they expect and is responsible for them while on site.
- Sees: Their own invitations and guests; Arrival notifications for their guests
- Does: Invites guests in advance with date, entrance and destination; Adds documents a guest must sign where allowed; Meets guests on arrival; Cancels invitations that are no longer needed
- Cannot: See other hosts' guests or the full visit log; Bypass screening or watchlist checks for their guest
- Approvals: Invitations for restricted areas may need approval from security, as your policy sets.
- Notified about: Their guest's arrival and any problem at sign-in.
Infection prevention lead
Infection preventionist, director of infection prevention, employee health lead. Sets health screening questions for visitors and changes them when conditions change.
- Sees: Screening questions by visitor type and site; Screening outcomes in summary; Change history for screening rules
- Does: Approves screening questions and what happens when a visitor does not pass; Requests changes when outbreak conditions change; Reviews screening outcomes in summary; Works with security on visitor restrictions for affected units
- Cannot: Change watchlist entries or sign-in flows outside screening; See individual visit records unless your policy allows
- Approvals: Approves changes to health screening; changes touching security rules also need the security director.
- Notified about: Screening changes applied and summaries of screening outcomes.
Privacy officer
Privacy officer, compliance officer. Decides what information is collected and kept about visitors and patients, and decides on privacy events.
- Sees: Data collected in each sign-in flow; Retention settings; Privacy events Moraph escalates
- Does: Approves what each sign-in flow collects, including whether a patient's name is recorded; Approves retention periods for visit records, photos and ID data; Decides on privacy events and whether notification is needed; Reviews Moraph staff access to the service
- Cannot: Change configuration directly; Delegate a breach notification decision to Moraph
- Approvals: Approves data collected and retention settings in the baseline with the security director.
- Notified about: Privacy events and changes to data collected or retained.
Moraph visitor platform engineer
Moraph workplace platform engineer. Configures and supports Envoy under change requests your organization has approved.
- Sees: Envoy administration settings within the service's scope; Device status for kiosks, printers and scanners; Tickets and the change record
- Does: Builds sign-in flows, questions and badges as approved; Configures sites, entrances and integrations; Sets up and supports kiosks, printers and ID scanners; Investigates second-line issues and escalates platform defects to Envoy; Applies watchlist entries only when security requests them
- Cannot: Approve a change they will apply; Decide who goes on the watchlist; Grant themselves additional administrator rights
- Approvals: Every change they apply has an approved request; emergency actions follow the agreed procedure and are reported straight away.
- Notified about: New tickets and requests, approvals granted, device problems and Envoy service notices.
Moraph service manager
Moraph service delivery manager. Runs the service, reports on it and makes sure requests, changes and escalations reach the right people.
- Sees: Service reporting, tickets, changes and escalations; Device inventory and licence use; Open actions from service reviews
- Does: Prepares and runs the monthly service review; Tracks requests, changes and escalations to closure; Reports licence and device needs; Coordinates with Envoy on platform incidents and service notices
- Cannot: Apply configuration changes; Make security, screening or privacy decisions
- Approvals: Recommendations go to the security director for a decision.
- Notified about: Escalations, overdue requests and platform incidents.
Permissions at a glance
| Action | Security lead | Desk officer | Host | Infection ctl | Privacy | Moraph eng. | Moraph service |
|---|---|---|---|---|---|---|---|
| Approve the configuration baseline | Approves | – | – | View | Approves | – | View |
| Request a configuration change | Full | – | – | Full | Full | – | – |
| Apply a configuration change | Approves | – | – | – | – | Full | – |
| Change health screening questions | View | – | – | Approves | View | Full | – |
| Add or remove watchlist entries | Approves | – | – | – | – | Full | – |
| Invite guests | Full | Full | Own work | Own work | – | – | – |
| Sign visitors in and print badges | Full | Full | – | – | – | – | – |
| Override a screening or watchlist outcome | Approves | Own work | – | – | – | – | – |
| Search and export visit records | Full | Own work | Own work | – | View | – | – |
| Set retention for visit data | Approves | – | – | – | Approves | Full | – |
| Grant Moraph administrator access | Approves | – | – | – | View | – | View |
| View change history | View | – | – | View | 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 engineers apply changes; your organization approves them. Nobody approves a change they requested themselves when a second approver is named.
- Watchlist decisions belong to your security team. Moraph enters or removes names only on a request from security, and watchlist matches are shown privately to the officers your procedure names.
- Desk officers and hosts are limited to their own site or guests. Roles can be limited by site and entrance, so a satellite clinic sees only its own visitors.
- Moraph staff use named, individual administrator accounts with only the rights the service needs. Every administrator action is recorded, and auditors get read-only evidence with a defined scope and 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.