Domain separation for Emergency Exposure Management

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 1 Minute Lesedauer

    • The following table lists the domain separation use cases for service providers (SPs) using this application.

    Hinweis:
    This information is subject to change: Limit use to SPs only.
    Tabelle : 1. Domain separation use cases for SPs
    Use case Functions Limitations
    SP Internal - SP uses the application for internal employees who might have collaborated with an affected internal employee. Yes None
    SP External - SP uses the application to identify employees (SP or tenant) who might have collaborated with an affected employee (SP or tenant). No Without the domain column, there is no base system platform security that prevents an SP user who has access to the application from seeing tenant information they would otherwise be restricted from seeing. “Limiting” Application Properties for Outlook settings.
    Tenant -Tenant uses the application to identify employees who might have collaborated with an affected employee. No Without the domain column, there is no base system platform security that prevents a tenant user with access to the application from seeing other tenant information they would otherwise be restricted from seeing. “Limiting” Application Properties for Outlook settings.

    Some modules in the Emergency Exposure Management application are affected by domain separation.

    CREATE NEW & ALL module (Diagnostic Request)
    • No domain column row protections or business logic exist.
    • Creates a Diagnostic Event based on Outlook meetings, exposure to an affected user, or the user's location, to identify users who might have been potentially exposed through collaboration.
    • Results from the Diagnostic Event return back to the Diagnostic Request or can be manually added.
    Hinweis:
    Because the Diagnostic Request record contains the User (Table: Sys_User) and Location (Table: Cmn_Location) fields, visibility to those reference fields is affected by domain separation. If a user is in a domain that does not have the appropriate visibilities granted, those fields appear empty in the Diagnostic Request even if they contain data.
    PROPERTIES module
    Standard Application Properties Page, all settings are global for the application.
    Hinweis:
    This property limits the ability of Outlook support in a domain-separated environment because tenants have different settings from the service provider.
    • No domain column row protections or business logic exist.
    • Captures the Outlook or Location responses and sends them back to the Diagnostic Request.
    • Purely an admin function.