Determination of user licences

Overview

For user-based billing, AppNavi determines licence usage when a user accesses an application integrated with AppNavi.

By default, AppNavi identifies a user using a browser-specific ID. A licence is assigned when a new user ID is created.

Important: The same person can use more than one licence if they access the application from different browsers or devices.

Required Role

You need access to the application's configuration/code to implement unique user identification.

If you only need to understand or review licence usage, no application code changes are required.

Prerequisites

Before configuring unique user identification, make sure:

The application is integrated with AppNavi.
A unique user identifier is available in the application, such as a user ID or email address.
JavaScript can access this identifier.
The application can call the AppNavi setguestuserid method.

How Licence Identification Works

Default behavior

When a user opens an integrated application:

AppNavi checks for appnavi_userid in the browser's local storage.
If it does not exist, AppNavi generates one and assigns a licence.
Returning to the same application using the same browser reuses the existing identification.
Accessing the application from another browser can result in another licence being assigned.

Cross-device identification

To identify the same user across different browsers or devices, configure setguestuserid.

The application provides AppNavi with a unique user identifier. AppNavi transfers this identifier as a hash so the user's licence can be consistently identified across browsers and devices.

Configuration

Use the setguestuserid method with a stable identifier from your application, such as the user's ID.

The identifier should uniquely represent the user and remain consistent across their sessions and devices.

For implementation details, see the setguestuserid documentation.

Licence Reset & Calculation

Licence usage is reset on the first day of each month.
A monthly statement records the number of user licences used.
At the end of each quarter, the average of the three monthly values is calculated.
AppNavi provides a 10% goodwill allowance because user identification can have some degree of imprecision.

Validation

After implementing unique user identification, verify:

Sign in as a test user.
Open an AppNavi-integrated application.
Verify that the user's unique ID is provided to AppNavi.
Open the same application from another browser or device.
Verify that the user is still identified as the same user.
Confirm that switching browsers/devices does not unnecessarily create another user licence.
Verify licence usage in the applicable monthly reporting.

Tip: Test with multiple browsers and devices because this is where incorrect user identification can result in additional licence assignments.

Security Considerations

The unique user identifier is transferred to AppNavi as a hash.

Use a stable, non-sensitive identifier intended for application user identification. Avoid exposing unnecessary personal information in the value passed to AppNavi.

Related Administration

Contracts — Review contract and licence information.
Assigning Applications — Manage which applications are assigned to the tenant/contract.
setguestuserid — Configure unique user identification across browsers and devices.