Organizational Unit

Overview

Organizational Unit recording lets you associate AppNavi activity with organizational information such as a department, business unit, or role. This helps you analyze application usage across different parts of your organization.

For example, if the organizational unit is set to Marketing, the recorded data can include that value so you can identify activity associated with the Marketing department.

The value is provided through the AppNavi Chrome Extension policy on each relevant device. Enabling the feature in the AppNavi Portal alone does not configure the value that the browser records.

Who should complete this setup?

This setup typically involves two roles:

• AppNavi Tenant Owner: Enables Organizational Unit recording in tenant settings.
• IT administrator: Configures the organizational unit value in the Chrome Extension policy and verifies that the browser applies it.

Coordinate these tasks before proceeding if you manage AppNavi but do not administer browser policies.

Before you start

Make sure you have:

• Access to the AppNavi Portal and the tenant settings.
• Access to the Windows device or browser policy configuration where the AppNavi Chrome Extension runs.
• An agreed format for organizational unit values, such as department names or business unit names.
• A reliable source for the user's organizational information, if the value will be populated automatically.

Recommended: Agree on consistent values before deployment. For example, use Marketing consistently rather than mixing Marketing, Marketing Team, and MKT. This makes the resulting data easier to interpret.

Onboarding workflow

Complete the following steps in order.

1. Enable Organizational Unit recording in AppNavi.
2. Configure the organizational unit value in the Chrome Extension policy.
3. Verify that the browser has applied the policy.
4. Confirm that the value is recorded in the relevant AppNavi data.
5. Continue to Insights or Discovery reporting, depending on your use case.

Step 1: Enable Organizational Unit recording

1. Sign in to the AppNavi Portal.
2. Open Manage Tenant and navigate to Settings.
3. Locate the Enable Organizational Unit setting.
4. Enable the setting and save the change if required by the interface.

This enables AppNavi to record organizational unit information. You must still configure the value supplied by the browser in the next step.

Expected result: Organizational Unit recording is enabled for the tenant.

Step 2: Configure the organizational unit value

The AppNavi Chrome Extension reads the organizational unit from the browser's managed policy. The current documentation provides a Windows Registry example for Google Chrome.

The policy key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\gldjdbpbhhpcpimpiicmglaeeehegflh\policy

Add or update the following string value:

The equivalent registry entry is:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\gldjdbpbhhpcpimpiicmglaeeehegflh\policy]
"OrganizationalUnit"="Marketing"

Replace Marketing with the organizational unit value appropriate for your organization.

Important considerations

• The documented maximum length is 128 characters.
• The registry example applies to Google Chrome on Windows. Confirm the appropriate deployment method for your organization's browser and device-management setup.
• If values are populated from a directory or anotherAfter configuring the registry, confirm that Google Chrome has applied the setting. identity source, your IT team must determine how to retrieve and apply those values according to your environment.

Expected result: The Chrome Extension policy contains the intended organizational unit value.

Step 3: Verify the browser policy

1. Open Google Chrome on the configured device.
2. Navigate to chrome://policy/.
3. Locate the AppNavi Chrome Extension policy.
4. Check that OrganizationalUnit appears with the expected value.
5. If the policy has not appeared or the value has not updated, allow a few minutes for the change to apply. Restarting the device may be necessary.

Expected result: The browser policy shows the intended organizational unit value.

If the value is missing or incorrect, review the registry path and value, and confirm that the browser has refreshed its policy before proceeding.

Step 4: Verify the recorded data

Once the tenant setting and browser policy are configured, verify the result in the relevant AppNavi data.

Verify in Insights

1. Open the relevant application's Insights data.
2. Download the UBM export.
3. Check whether the recorded events include the expected organizational unit value.

The value can be used to identify recorded activity associated with the relevant organizational unit.

Verify in Discovery

If you also need organizational unit information in Discovery:

1. Open Discovery in the AppNavi Portal.
2. Open the Discovery settings.
3. Enable organizational unit recording for Discovery, where available.
4. Review the discovered applications data or download the export.
5. Check whether the expected organizational unit value is present.

Expected result: The relevant export contains the organizational unit value for recorded data where the feature is configured and the value is available.

If the value is not present, check the tenant setting, browser policy, and Discovery-specific setting. Also allow time for the configuration to take effect and for new activity to be recorded.

Step 5: Continue your AppNavi setup

After verifying the value, continue with the workflow that matches your objective:

• Analyze application usage: Use Insights data to review recorded activity. See Insights documentation.
• Analyze discovered applications: Continue configuring Discovery and review the discovered applications data. See App Discovery.
• Review tenant configuration: See Manage Tenant and Settings.

Troubleshooting

Example : Reading configuration from Microsoft Graph API

Here is a simple example of how to read a user's department from the Graph API and then write the value to the registry.

IMPORTANT: This is only an example. Depending on your IT organization and the guidelines and requirements, the script must be designed differently.

Install-Module Microsoft.Graph -Scope CurrentUser
Connect-MgGraph

#Get the current user
$user = Get-MgUser -UserId "[email protected]"

# Print specific properties, such as company
Write-Output "First Name: $($user.GivenName)"
Write-Output "Last Name: $($user.Surname)"
Write-Output "Display Name: $($user.DisplayName)"
Write-Output "Company Name: $($user.CompanyName)"
Write-Output "Department: $($user.Department)"
Write-Output "Job Title: $($user.JobTitle)"

# Create the registry key and set the value in one line
New-Item -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\gldjdbpbhhpcpimpiicmglaeeehegflh\policy" -Force | Out-Null

# Updates the Department for Google Chrome browser policy
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\gldjdbpbhhpcpimpiicmglaeeehegflh\policy" -Name "OrganizationalUnit" -Value $($user.Department)