| \n\nType\n\n | \n\nInstructions\n\n |
|---|---|
| \n\nCommercial on-premise\n\n | \n\nVisit the ServiceNow® Store to download and install the application.\n\n |
| \n\nFederal hosted\n\n | \n\nSee the [Federal downloads for the Emergency Response Management and Safe Workplace suite apps \\[KB0030260\\]](https://store.servicenow.com/$appstore.do#!/store/help?article=KB0030260) article in the Store Help Center for more information.\n\n |
| \n\nFederal on-premise\n\n | \n\nIf you are a federal on-premise customer and you would like to install this application, reach out to your sales representative or open a Now Support or HIWAVE ticket. In the ticket, request to be routed to the SHOT team.\n\n See the [Federal downloads for the Emergency Response Management and Safe Workplace suite apps \\[KB0030260\\]](https://store.servicenow.com/$appstore.do#!/store/help?article=KB0030260) article in the Store Help Center for more information.\n\n |
| \n\nOn-premise\n\n | \n\nSee the [Commercial downloads for the Emergency Response Management and Safe Workplace suite apps \\[KB0030258\\]](https://store.servicenow.com/$appstore.do#!/store/help?article=KB0030258) article in the Store Help Center for more information.\n\n |
| \n\nRole title \\[name\\]\n\n | \n\nDescription\n\n | \n\nContains roles\n\n |
|---|---|---|
| \n\nContact Tracing admin\\[sn\\_imt\\_tracing.admin\\]\n\n | \n\nApplication-specific admin for Contact Tracing and has administrative privileges.\n\n | \n\n- sn\\_imt\\_tracing.case\\_manager\n- sn\\_imt\\_tracing.badge\\_admin\n- sn\\_imt\\_tracing.contact\\_tracing\\_user\n\n |
| \n\nContact tracing user\\[sn\\_imt\\_tracing.contact\\_tracing\\_user\\]\n\n | \n\nCan submit daily contacts log and privacy consent preference, and access contact tracing cases when added to the case watch list.\n\n | \n\n- sn\\_imt\\_checkin.dailylog\\_user\n- sn\\_imt\\_tracing.privacy\\_consent\\_user\n\n |
| \n\nBadge admin\\[sn\\_imt\\_tracing.badge\\_admin\\]\n\n | \n\nCan create, update, delete, and import badge data.\n\n | \n\nsn\\_imt\\_tracing.badge\\_manager\n\n |
| \n\nBadge manager\\[sn\\_imt\\_tracing.badge\\_manager\\]\n\n | \n\nCan create, update, and import badge data.\n\n | \n\n- sn\\_imt\\_tracing.badge\\_reader\n- import\\_admin\n\n |
| \n\nBadge reader\\[sn\\_imt\\_tracing.badge\\_reader\\]\n\n | \n\nCan view badge access register data.\n\n | \n\nNone\n\n |
| \n\nCase manager\\[sn\\_imt\\_tracing.case\\_manager\\]\n\n | \n\nCan create and manage outreach cases, run diagnostic requests to identify potentially exposed contacts. Can create, assign, and supervise tasks.\n\n | \n\n- sn\\_imt\\_diagnosis.diagnostics\\_admin\n- sn\\_imt\\_tracing.contact\\_tracer\n\n |
| \n\nContact tracer\\[sn\\_imt\\_tracing.contact\\_tracer\\]\n\n | \n\nCan work on assigned case tasks to follow up on the health status of potentially exposed contacts, as per the predefined instructions.\n\n | \n\n- task\\_editor\n- survey\\_reader\n\n |
| \n\nPrivacy consent user\\[sn\\_imt\\_tracing.privacy\\_consent\\_user\\]\n\n | \n\nCan submit and update the user policy consent for themselves.\n\n | \n\nNone\n\n |
| \n\nTracing user\\[sn\\_imt\\_tracing.dailylog\\_user\\]\n\n | \n\nCan fill in the daily contacts log to submit a list of users that they interacted with at the workplace.\n\n | \n\nNone\n\n |
| \n\nWi-Fi admin\\[sn\\_imt\\_tracing.wifi\\_admin\\]\n\n | \n\nCan create, update, delete, and import Wi-Fi access logs.\n\n | \n\nsn\\_imt\\_tracing.wifi\\_manager\n\n |
| \n\nWi-Fi manager\\[sn\\_imt\\_tracing.wifi\\_manager\\]\n\n | \n\nCan create, update, and import Wi-Fi access Logs.\n\n | \n\n- import\\_admin\n- sn\\_imt\\_tracing.wifi\\_reader\n\n |
| \n\nWi-Fi reader\\[sn\\_imt\\_tracing.wifi\\_reader\\]\n\n | \n\nCan view Wi-Fi access logs.\n\n | \n\nNone\n\n |
| \n\nWearable admin\\[sn\\_imt\\_tracing.wearable\\_admin\\]\n\n | \n\nCan create, update, delete, and import handheld or wearable devices access logs.\n\n | \n\nsn\\_imt\\_tracing.wearable\\_manager\n\n |
| \n\nWearable manager\\[sn\\_imt\\_tracing.wearable\\_manager\\]\n\n | \n\nCan create, update, and import handheld or wearable devices access logs.\n\n | \n\nsn\\_imt\\_tracing.wearable\\_reader\n\n |
| \n\nWearable reader\\[sn\\_imt\\_tracing.wearable\\_reader\\]\n\n | \n\nCan view handheld or wearable device access logs.\n\n | \n\nNone\n\n |
| \n\nScheduled job\n\n | \n\nDescription\n\n |
|---|---|
| \n\nData Retention Job For Contact Tracing\n\n | \n\nDeletes contact tracing data after the retention period is over from the last updated date for the records related to contact tracing. The data includes badge swipes, Wi-Fi access register data,employee daily contact logs, daily log notes, and daily log acknowledgements, cases and associated case tasks, exposed contacts, diagnostic requests, diagnostic jobs, and workplace reservations.\n\n**Note:** The data retention policy doesn't apply to user privacy consent data.\n\n |
| \n\nDevvio\n\n Integration\n\n | \n\nRuns daily at 00:00:00 instance time and populates the Devvio Users Risk Report for organizations that use Devvio wearables and the DevvTrace platform.\n\n |
| \n\nLoad Mist Systems\n\n | \n\nRuns daily at 00:00:00 and populates the sites for the organizations that use Wi-Fi logs from Mist Systems.\n\n |
| \n\nTable\n\n | \n\nDescription\n\n |
|---|---|
| \n\nBadge Access Register\\[sn\\_imt\\_tracing\\_badge\\_access\\_register\\]\n\n | \n\nBadge swipe records of all users.\n\n |
| \n\nBadge Access Register Stage\\[sn\\_imt\\_tracing\\_badge\\_access\\_register\\_stage\\]\n\n | \n\nThe Import Set table for importing the badge access data from an Excel spreadsheet. When you load data from the Excel file into the application, the imported records are first saved in this import set table. After you run the transform, or execute the scheduled import script, the records are copied from this table to the Badge Access Register table.\n\n |
| \n\nBadge Reader\\[sn\\_imt\\_tracing\\_badge\\_reader\\]\n\n | \n\nUser ID badge reading devices installed in a location.\n\n |
| \n\nUser Badge\\[sn\\_imt\\_tracing\\_user\\_badge\\]\n\n | \n\nUsers and their ID badge information.\n\n |
| \n\nCase\\[sn\\_imt\\_tracing\\_case\\]\n\n | \n\nOutreach cases for affected users to help minimize potential exposure to others.\n\n |
| \n\nCase Task\\[sn\\_imt\\_tracing\\_case\\_task\\]\n\n | \n\nCase tasks in outreach cases to follow up with the potentially exposed users to track health status.\n\n |
| \n\nExposed Contacts\\[sn\\_imt\\_tracing\\_exposed\\_contact\\]\n\n | \n\nPotentially exposed users that might have interacted with a user who has been diagnosed with an infectious disease. The records in this table are stored when the case manager adds all impacted users to the case. Impacted users are identified through the diagnostic request using multiple data input.\n\n |
| \n\nDaily Contact Logs\\[sn\\_imt\\_tracing\\_daily\\_contact\\_log\\]\n\n | \n\nThe names of users submitted using daily contact logs by another user.\n\n |
| \n\nDaily Log Acknowledgements\\[sn\\_imt\\_tracing\\_daily\\_log\\_acknowledgement\\]\n\n | \n\nAcknowledgement status to identify which users have responded to the notification to submit the daily contacts log.\n\n |
| \n\nDaily Log Notes\\[sn\\_imt\\_tracing\\_daily\\_log\\_note\\]\n\n | \n\nNames of users outside of the organization, such as visitors and contractors submitted using daily contact logs by another user.\n\n |
| \n\nDevvio Users Risk Report\n\n \\[sn\\_imt\\_tracing\\_devvio\\_users\\_risk\\_report\\]\n\n | \n\nDevvio users and their risk scores captured by Devvio wearables. The records in this table are imported from the DevvTrace platform and updated daily.\n\n |
| \n\nLocation Privacy Configuration\\[sn\\_imt\\_tracing\\_location\\_privacy\\_config\\]\n\n | \n\nConfiguration for the location-based privacy policy, such as the privacy statement for a location and whether a particular location requires privacy consent.\n\n |
| \n\nPrivacy Consent Template\\[sn\\_imt\\_tracing\\_privacy\\_consent\\_template\\]\n\n | \n\nTemplate to store the privacy statement for a location and is used in the location privacy configuration.\n\n |
| \n\nUser Privacy Notice and Consents\\[sn\\_imt\\_tracing\\_user\\_privacy\\_consent\\]\n\n | \n\nResponses of users to the privacy consent.\n\n |
| \n\nSites\\[sn\\_imt\\_tracing\\_site\\]\n\n | \n\nSites in the building of your organization. Each floor is considered as a site. Each site can be further divided into zones. Each zone can have multiple Wi-Fi routers installed, called as Wi-Fi access points.\n\n |
| \n\nWi-Fi Diagnostic Preferences\\[sn\\_imt\\_tracing\\_wifi\\_diagnostic\\_preference\\]\n\n | \n\nType of Wi-Fi data used for contact tracing. For example, you might have real-time data for a location collected through the integration with a network system, such as Mist Systems. For other locations, you might manually upload data from a spreadsheet.\n\n |
| \n\nWi-Fi Access Register\\[sn\\_imt\\_tracing\\_wifi\\_access\\_register\\]\n\n | \n\nEntry and exit time records of users who have connected to the office Wi-Fi access pointsor using the BLE enabled devices.\n\n |
| \n\nWearable Access Register\\[sn\\_imt\\_tracing\\_wearable\\_access\\_register\\]\n\n | \n\nUser interaction records captured using the proximity sensing data via their handheld or wearable devices when they are in the close proximity for more than the permissible time.\n\n |