Application Visibility Mode

Avatar Visibility Mode lets you control whether the AppNavi avatar is shown to users within an application. This feature is commonly used to limit avatar visibility during testing, phased rollouts, or controlled enablement for specific user groups.

Two visibility modes are available:

• Visible
• Restricted

Visible Mode

When an application is set to Visible mode:

• The avatar is visible to all users of the application.
• No target audience configuration is required.
• All AppNavi features (Routes, Announcements, Insights, Custom Code) behave normally.

This mode is recommended for production environments where AppNavi should be available to everyone.

Restricted Mode

When Restricted mode is enabled, avatar visibility becomes conditional.

Default Behavior

• Restricted mode ON → Avatar is invisible for all users by default (including tenant owners).
• The application continues to function in the background.

Target Audience Configuration

• One or more Target Audiences (TA) can be added.
• The avatar becomes visible only for users who fall within the configured Target Audiences.
• Users not matching any TA will not see the avatar.

This allows precise control over who can access AppNavi within the application.

How to Set Avatar Visibility Mode

Visibility mode can be configured during application creation or edited later.

1. Go to Applications.
2. Select an application from the list.
3. Click the three dots and choose Edit.
4. Navigate to Avatar Visibility.
5. Select Visible or Restricted from the dropdown.
6. Add one or more Target Audiences when using Restricted mode- Optional
7. Save the changes.

Restricted Mode – Feature Behaviour Overview

Restricted mode affects avatar visibility only. Other AppNavi functionalities may still operate depending on the scenario.

Following table shows behaviour of Restricted Mode with and without Target Audiences.

Routes with Restricted Mode

• Routes require the avatar to be visible in order to be launched.
• If Restricted mode is ON without a Target Audience, routes cannot be started because the avatar is hidden.
• If Restricted mode is ON with a Target Audience, routes are available only to users included in the TA.

Example:

• Application in Restricted mode
• Target Audience = QA Team
• Only QA users can see the avatar and play routes

PINS with Restricted Mode

• Pins display doesn't require the avatar to be visible in order to be launched.
• If Restricted mode is ON without a Target Audience, Pins will be continue to displayed to end users.
• If Restricted mode is ON with a Target Audience, Pins will remain available depending on it's own configured target audiences.

Announcements with Restricted Mode

• Announcements are not dependent on avatar visibility.
• Even when Restricted mode is ON and no avatar is visible, announcements will still be displayed to users.

Example:

• Application in Restricted mode
• No Target Audience configured
• Users will still receive announcements

Insights with Restricted Mode

• Insights recording works independently of avatar visibility.
• User interactions continue to be tracked even when the avatar is hidden.

Example:

• Restricted mode enabled
• No TA configured
• Avatar hidden, but Insights data is still captured
• Surveys will be displayed

Custom Code and Restricted Mode

Custom code execution is not blocked by Restricted mode.

• Custom code has higher priority than visibility mode.
• If Restricted mode is ON and custom code explicitly calls showAvatar():
  • The avatar will be displayed, regardless of Target Audience configuration.
• Similarly, If Restricted mode is ON and custom code explicitly calls startRoute():
  • The route will be played, regardless of Target Audience configuration.

NOTE:

• If a user is already logged in and the application visibility is changed to Restricted mode, The avatar will continued to be displayed.
• Restricted mode controls visibility only, not feature execution.
• Insights, Announcements, Surveys, Pins and Custom code continue to function even when the avatar is hidden.
• Custom code always takes precedence over visibility restrictions.