Decision guide for your organization hierarchy

Note

The information in this article doesn't apply to Dragon Copilot (radiologists).

This article provides recommendations and example scenarios to help you build your organization hierarchy in Dragon admin center.

Organization hierarchy concept

When you create an environment, it includes one default organizational unit as the root unit. You can create additional units as child units of the root unit. When you create additional units, you can select any existing unit as the parent of the new unit. For example:

Example organization hierarchy consistof a root unit, parent units, and child units

You can assign users to one or more organizational units. If you don't explicitly assign users to a unit, they are implicitly assigned to the root unit.

Each organizational unit acts as a container for Dragon Copilot settings and library items. The settings and library items configured for a higher-level unit cascade down to its child units.

Your organization hierarchy connects your users with the settings and library items they need when they work with Dragon Copilot.

Adding and assigning users to organizational units

Healthcare groups and Microsoft Entra ID security groups can add multiple user accounts to organizational units. Adding and assigning users in bulk is more efficient. Use healthcare groups when you want to use Dragon admin center to manage groups. Use Entra security groups when user accounts are already maintained via Microsoft Entra ID or there are frequent changes and you want to reuse that existing group.

For more information, see:

Recommendations

You can create as many or as few organizational units as you need and define their hierarchy flexibly. Use the following recommendations:

  • Keep the organization hierarchy as simple as possible.

  • Plan your organization hierarchy carefully.

  • Consider whether you need to create the hierarchy based on the structure of the organization (for example: region > department) or based on the configurations required by different groups of users.

  • If you maintain group membership in Microsoft Entra ID, consider connecting an Entra security group to the organizational unit instead of recreating the same group in Dragon admin center.

  • Use organizational units to model configuration inheritance, and use groups to simplify user assignment at scale.

  • Use direct user assignment for exceptions or smaller sets of users that don't need ongoing centralized membership management.

Scenarios

The following example scenarios help you get started with direct assignments and group-based assignments for organizational units.

Scenario 1 - customize settings for users with different needs across an organization

Contoso Memorial Hospital has three departments that implement Dragon Copilot (physicians): Dermatology, Internal Medicine, and Pediatric Medicine.

  • In the Dermatology department, some users want to use only dictation, some want to use only generative AI features, and some want to use both features.

  • In the Internal Medicine department, some users don't want to use the Information Assist feature.

  • Pediatric Medicine wants to use all features and functionality.

In this example, you create three parent organizational units for Dermatology, Internal Medicine, and Pediatric Medicine under the root unit of Contoso Memorial Hospital.

In the unit of Dermatology, create two child units:

  • Child unit - Generative AI Only Users: Turn off the Dragon Copilot (physicians) settings for speech-to-text/dictation and turn on the generative AI settings.

  • Child unit - Speech to Text Only Users: Turn off the Dragon Copilot (physicians) generative AI settings and turn on the speech-to-text/dictation settings.

Add users that request one of those configurations to the appropriate unit. Users that want both features enabled stay in the parent unit of Dermatology.

In the unit of Internal Medicine, create one child unit:

  • Child unit - No Information Assist Users: Turn off Information Assist for that unit.

Add users that want this configuration.

In the unit of Pediatric Medicine, you don't need a child unit because the Pediatric department wants all features enabled for their users.

The structure for this scenario looks like this:

The organizational unit structure for Contoso Memorial Hospital. The root unit is Contoso Memorial Hospital - Production. Under the root unit are three parent units: Dermatology, Internal Medicine and Pediatric Medicine. Under the parent unit of Dermatology there are two child units, Generative AI Only users and Speech to Text Only users. Under the parent unit of Internal Medicine there is one child unit of No Information Assistant users.

Scenario 2 - enable settings for a subset of users

Contoso Clinic wants to test a new feature in Dragon Copilot. Currently, all their users are in the root organizational unit, called Contoso Clinic.

  1. Add a new unit under the root unit of Contoso Clinic.
  2. Turn on the settings for the new feature for that unit.
  3. Add users who are testing the new feature to that unit.

The structure for this scenario looks like this:

The root organizational unit of Contoso Clinic with a parent unit called New Feature Test

Scenario 3 - share texts and prompts with a subset of users

Contoso Medical Group wants to share some custom texts and prompts with their pathologists only. Currently, all their users are in the root organizational unit, called Contoso Clinic.

  1. Add a new unit, Pathology, under the root unit of Contoso Clinic.
  2. Create texts and prompts for that unit.
  3. Add Pathology users to that unit.

The structure for this scenario looks like this:

A screenshot of the root organizational unit of Contoso Clinic with one parent unit of Pathology

Scenario 4 - use Microsoft Entra ID groups or healthcare groups to manage shared users across organizational units

Contoso Medical Group has two facilities called East and West.

  • Some providers alternate between facilities throughout the week.

  • Each facility has its own custom texts that it needs to share with members.

For users who work at only one facility:

  1. Create two units, East and West.
  2. In each unit, add the custom texts that they require.
  3. Add users who work only at East to the East unit.
  4. Add users who work only at West to the West unit.

For users who work at both facilities:

  • If the Shared Clinicians group already exists in Microsoft Entra ID:

    1. Connect the Entra security group called Shared Clinicians to the appropriate organizational unit or units.
    2. Use Microsoft Entra ID to manage membership for this group as clinicians start or stop working across facilities. Membership for connected Entra security groups is read-only in Dragon admin center.

  • If you need a Dragon admin center group:

    1. Create a healthcare group called Shared Clinicians.
    2. Add or remove this group from the East unit and West unit as needed.

Scenario 5 - connect an existing Microsoft Entra ID group to an organizational unit

Contoso manages user membership centrally in Microsoft Entra ID. You connect the existing department-based Entra security group to the corresponding organizational unit. Membership changes continue to be managed in Microsoft Entra ID and the organizational unit continues to provide the appropriate settings and library items for those users. You don't need to create the same group membership in Dragon admin center.

Related content

  • Last updated on