Applications

Overview

Applications are the foundation of AppNavi. An application connects AppNavi to a browser-based business application and defines where AppNavi appears, how the avatar behaves, and which authentication and execution options are used.

Applications are managed from Manage Tenant → Applications. A tenant can contain multiple applications, and each application can be assigned to a workspace and contract.

Required role: Tenant Owner. Only Tenant Owners can add, edit, or delete applications.

Application Settings

Setting	Purpose	Default / Notes
Application Name	Name used to identify the application in AppNavi.	Required
Application URL	Main URL of the application.	Required
Pattern	Defines the URLs where AppNavi should run. Use `*` to include additional pages.	Generate it after entering the URL
Language	Controls the language of AppNavi content.	Browser language
Avatar Position	Determines where the AppNavi avatar appears.	Bottom Left
Avatar Visibility	Controls who can see the AppNavi avatar.	Visible
Code Execution Mode	Determines how AppNavi custom code is executed.	Dynamic
Authentication Mode	Determines which login methods are available.	Username/Password and/or SSO
Application Disabled	Temporarily prevents AppNavi from running on the application.	Disabled

Important Settings

URL & Pattern

Enter the application's main URL, then generate the Pattern.

Use a wildcard such as * when AppNavi should be available across multiple pages.

Learn more: Create an Application

Avatar Visibility

Visible — Avatar is available to users.
Restricted Mode — Avatar is initially hidden and can be shown only when the configured restriction key is present.

Restricted Mode is useful for testing or controlled rollouts. Up to five restriction keys can be configured.

Security: Restriction keys control avatar visibility, but they do not disable other AppNavi functionality such as analytics recording or custom code.

Learn more: Application Visibility Mode

Code Execution Mode

Dynamic (eval) — Default and recommended option.
Inline — Places custom code inside a script tag and may be affected by the application's Content Security Policy (CSP).

Use Inline only when Dynamic causes compatibility issues.

Security: Changing the execution mode can affect how custom code interacts with your application's CSP. Validate the application after making this change.

Authentication Mode

You can enable:

Username/Password
Single Sign-On (SSO)

Multiple authentication modes can be enabled when required.

Save & Validate

After creating or editing an application:

Complete the required settings.
Click Save Changes.
Open the configured application URL.
Confirm that AppNavi loads according to the configured Pattern.
Verify the avatar appears in the selected position and visibility mode.
If authentication was changed, verify the configured login option works.
If custom code or execution mode was changed, verify that the application continues to function correctly.

Tip: Always test the actual application URL after saving. A correct application configuration in the Portal does not necessarily mean the configured URL or CSP settings will work as expected in the target application.

Related Configuration

Create your first Application — Step-by-step application setup
Application Visibility Mode — Configure Visible or Restricted Mode
Content Publication — Control which Routes, Posts, Announcements, Collections, and Pins appear in an application
AppNavi Guide API — Control application and avatar behavior through APIs`