The Settings page is the central configuration area for managing tenant-wide AppNavi behavior.

Use this page to configure settings that affect authentication, AI capabilities, application discovery, Guidance, organizational data, custom development, notifications, and other tenant-level functionality.

Settings are managed from Manage Tenant → Settings.

Required role: Tenant Owner. Tenant-level settings can affect multiple workspaces, applications, and users, so review the impact of a setting before enabling or changing it. AppNavi uses a multi-tenant structure, with tenant-level configuration applying across the tenant.

---

When to Use Settings

Use the Settings page when you need to:

• Enable or disable tenant-level AppNavi functionality.
• Configure authentication and security options.
• Connect an Identity Provider (IdP).
• Enable AI-powered functionality.
• Configure application discovery.
• Enable content import for Guidance.
• Configure organizational-unit tracking.
• Configure Client API access.
• Configure tenant notification contacts.
• Select the currency used by financial or transactional features.
• Enable advanced custom-code functionality.

Settings are organized into sections so that related configuration can be managed together.

---

Before You Start

Before changing a tenant setting:

1. Confirm that you are a Tenant Owner.
2. Identify the functionality you want to configure.
3. Review the related documentation for the setting.
4. Gather any information required by the external system if you are configuring authentication or an IdP.
5. Understand whether the setting affects the entire tenant, specific applications, or specific users.
6. If the setting is security-related, coordinate the change with the appropriate security or identity administrator.
7. Save the configuration.
8. Test the affected functionality after saving.

Tip: Do not enable a setting simply because it is available. First confirm that the related feature is required and that its prerequisites have been completed.

---

Settings Workflow

Use this general workflow for tenant configuration:

1. Open Settings

Go to:

Manage Tenant → Settings

2. Find the Required Section

Settings are grouped into:

• Basic Settings
• AI Settings
• Authentication Settings
• End-User Authentication (IdP)
• Portal & Avatar Authentication (SSO)
• Guidance Settings
• Discovery Settings
• Email Notifications

3. Review the Current Configuration

Before changing a setting, check whether it is currently enabled and review any existing values.

4. Configure the Setting

Enable, disable, or update the required configuration.

For settings that require additional values, enter the information provided by the relevant administrator or external service.

5. Save the Changes

Save the configuration after completing the required fields.

6. Validate

Test the functionality affected by the setting.

For example:

• Test authentication after changing authentication settings.
• Test discovery after enabling Discovery.
• Test Guidance content import after configuring Content Import.
• Verify notifications after adding notification recipients.

---

Basic Settings

Basic Settings control tenant-level platform capabilities and general configuration.

Activate Expert Mode

Purpose:
Enables users to write custom code within the application.

Use this setting when advanced users need additional customization capabilities.

Considerations:

• Intended for advanced users.
• Custom code can affect application behavior.
• Test custom code before making changes available to end users.

Expected Outcome

Users with access to the relevant functionality can use custom-code capabilities according to their permissions.

For additional guidance, see the AppNavi Guide API documentation.

---

Enable Organizational Unit

Purpose:
Enables organizational-unit information for reporting and management.

Use this setting when your organization needs to work with organizational units as part of its AppNavi data and reporting structure.

Expected Outcome

Organizational-unit information can be used where supported by AppNavi reporting and management functionality.

---

Enable Client API

Purpose:
Enables configuration and management of Client APIs.

Use this setting when your AppNavi implementation requires Client API functionality.

Expected Outcome

Client API configuration becomes available for the tenant.

For implementation-specific API guidance, see the relevant AppNavi API documentation.

---

Currency

Purpose:
Defines the preferred currency used by AppNavi financial or transactional features.

Default: EUR

Select the currency that should be used when financial values are displayed or calculated.

Expected Outcome

Supported financial or transactional features use the configured currency.

---

AI Settings

Enable AI Features

Purpose:
Activates AI-powered functionality across AppNavi.

Enable this setting when your organization wants to use AppNavi features that depend on tenant-level AI functionality.

Before You Enable It

Confirm:

• Your organization intends to use AI-powered AppNavi functionality.
• Any feature-specific prerequisites have been completed.
• Relevant administrators understand which AI functionality will become available.

Expected Outcome

AI-powered functionality that depends on the tenant-level AI setting becomes available.

Important: Some AppNavi features have an additional feature-specific AI setting. For example, Discovery ASK requires both the tenant-level Enable AI Features setting and the Discovery-level Enable Discovery AI Features setting.

Related Documentation

See the documentation for the specific AI feature you want to enable before changing this setting.

---

Authentication Settings

Authentication Settings control how users authenticate with AppNavi.

The General Authentication section includes:

• Activate MFA
• Auto Logout
• Domain Restrictions

---

Activate MFA

Purpose:
Adds multi-factor authentication to the login process.

Use MFA when your organization requires an additional authentication factor beyond the primary login credentials.

Expected Outcome

Users are required to complete the configured multi-factor authentication flow during login.

Recommended Validation

After enabling MFA:

1. Sign in with a test account.
2. Confirm that the additional authentication step appears.
3. Complete the authentication challenge.
4. Confirm that the user can access the AppNavi Portal successfully.

---

Auto Logout

Purpose:
Automatically logs users out after a configured period of inactivity.

Use Auto Logout when your organization wants inactive AppNavi sessions to expire automatically.

Recommended Use

Auto Logout is particularly useful when tenant security requirements require inactive sessions to be closed.

Expected Outcome

Users who remain inactive for the configured period are automatically logged out.

Recommended Validation

Test the configured timeout using a test account and confirm that:

• The inactivity period is applied.
• Any configured warning appears as expected.
• The user is logged out when the timeout is reached.
• The user can sign in again normally.

---

Domain Restrictions

Purpose:
Restricts login and user creation to approved email domains.

Use Domain Restrictions when only users belonging to specific organizational domains should be allowed to access or be created in the tenant.

Configuration

Add the domains that should be permitted.

Example

An organization uses:

company.com

as its corporate email domain.

The administrator can configure the tenant to allow the approved domain and prevent unauthorized domains from being used for applicable login or user-creation flows.

Expected Outcome

Only users matching the configured domain restrictions are allowed through the affected authentication or user-creation flows.

Recommended Validation

Test with:

• An approved domain account.
• An account using a non-approved domain.

Confirm that the restriction behaves as expected.

---

End-User Authentication (IdP)

Identity Connect

Purpose:
Connects AppNavi to your organization's Identity Provider (IdP) for end-user authentication.

The current Settings documentation specifies support for Okta, Google, and Microsoft Entra as authentication providers, and Identity Connect works with the AppNavi Chromium extension.

Use Identity Connect when your organization wants AppNavi to obtain authenticated user information from an existing identity system instead of maintaining that information separately.

What You Need Before Configuration

Obtain the required OIDC information from your Identity Provider, including the applicable:

• Authorization URI
• Token URI
• UserInfo URI
• Client ID
• Client Secret, where required
• Scopes
• Claim fields

The exact values depend on your identity provider.

Configuration

1. Go to Manage Tenant → Settings.
2. Open End-User Authentication (IdP).
3. Enable the Identity Provider option.
4. Select the authentication provider.
5. Enter the required authentication, token, and UserInfo endpoints.
6. Configure Scopes and Claim Fields.
7. Enter the Client ID and other required credentials.
8. Select the required Interactive Mode.
9. Save the configuration.
10. Use Test Configuration, where available, to validate the setup.

Interactive Modes

The available modes determine how users are prompted during authentication:

• Silent Login — attempts to authenticate without user interaction when a valid session exists.
• Force Login — requires the user to sign in.
• Force Consent — requests user consent for the configured permissions.

Expected Outcome

After successful configuration, AppNavi can authenticate the user through the configured IdP and retrieve the configured profile claims.

Validation

Use the Identity Connect test functionality to verify the configuration before asking users to authenticate.

A successful test should return the expected provider and user information. If authentication fails, review the Client ID, endpoints, scopes, claims, and provider configuration.

Related Documentation

See End User Authentication for provider-specific setup, OIDC configuration, testing, troubleshooting, and claim validation.

---

End-User Authorization

Purpose:
Controls whether IdP-based authentication is enabled for secure access.

Use this setting together with the Identity Connect configuration when your implementation requires end-user authorization.

Expected Outcome

When correctly configured, authenticated users can access the relevant AppNavi functionality using the configured identity flow.

Important: Identity Connect, End-User Authorization, and application-level authentication settings can interact. Review the authentication documentation before changing these settings.

---

Authentication Provider

Select the Identity Provider used for the end-user authentication configuration.

The Settings page currently lists:

• Okta
• Google
• Microsoft Entra

Select the provider that matches your organization's IdP configuration.

---

Authorization / Token / UserInfo URIs

These fields define the endpoints AppNavi uses during the authentication process.

• Authorization URI — used to initiate authentication.
• Token URI — used to obtain tokens.
• UserInfo URI — used to retrieve user profile information.

Enter the values supplied by your Identity Provider.

---

Scopes and Claim Fields

Scopes define the information and permissions requested from the Identity Provider.

Claim Fields define the user attributes that AppNavi should retrieve.

Examples may include:

• Name
• Email
• Department

Claims can subsequently support reporting, targeting, personalization, and other AppNavi functionality.

---

Client ID and Interactive Mode

Client ID identifies the configured application in the Identity Provider.

Interactive Mode determines how authentication prompts are handled.

Use the values provided by your Identity Provider and select the authentication behavior required by your organization.

---

Portal & Avatar Authentication (SSO)

Enable Single Sign-On (SSO)

Purpose:
Allows users to authenticate using the organization's configured SSO provider.

Use this setting when AppNavi Portal and Avatar authentication should use an organization's SSO configuration.

Configuration Information

Depending on the SSO configuration, the following values may be required:

• Callback URI
• Authorization URI
• Token URI
• UserInfo URI
• Issuer URL
• Client ID
• Client Secret
• Claim Field
• Authentication Context Class Reference

Optional settings include:

• Enable Query String
• Ignore Entity Details

Expected Outcome

Users can authenticate using the configured SSO flow.

Validation

After saving:

1. Sign out of AppNavi.
2. Start the login process again.
3. Confirm that the configured SSO option is available.
4. Complete authentication.
5. Confirm that the user is returned to AppNavi successfully.

Important: Keep Client Secrets confidential. Only authorized administrators should have access to them.

Related Documentation

See the authentication documentation for the detailed SSO/OIDC configuration required by your identity provider.

---

Guidance Settings

Enable Content Import

Purpose:
Adds the Content Import capability to the Guidance module.

Use this setting when your organization wants to import supported guidance content from an external content provider.

Content Providers

Select the content providers that should be available for content import.

The current Settings documentation gives WalkMe as an example of a content provider.

Configuration Workflow

1. Open Manage Tenant → Settings.
2. Go to Guidance Settings.
3. Enable Content Import.
4. Select the required content provider.
5. Save the configuration.
6. Open the Guidance module.
7. Confirm that the Content Import functionality is available.
8. Test the import using the configured provider.

Expected Outcome

Content Import becomes available in the Guidance module for the configured provider.

Related Documentation

Review the Guidance and content-import documentation before importing production content.

---

Discovery Settings

Enable App Discovery

Purpose:
Activates application discovery functionality within AppNavi.

Use App Discovery when your organization wants AppNavi to discover and analyze applications based on the configured discovery data source.

Configuration Workflow

1. Open Manage Tenant → Settings.
2. Locate Discovery Settings.
3. Enable App Discovery.
4. Select the required data source.
5. Save the configuration.
6. Open the Discovery area.
7. Confirm that discovery functionality is available.
8. Verify that data begins appearing according to the selected source and discovery configuration.

Data Source

The current Settings page provides two options:

• Extension
• Defender API

Select the source that matches your organization's Discovery implementation.

Expected Outcome

Application Discovery is enabled and AppNavi can use the selected source for discovery data.

Related Documentation

See the App Discovery documentation for discovery configuration, discovered applications, analytics, governance, and related functionality.

---

Email Notifications

The Email Notifications section allows Tenant Owners to define contacts for different types of AppNavi communications.

Each category supports up to 5 email addresses.

Release and Update Notification Emails

Use this field for recipients who should receive product release and update notifications.

Maximum: 5 email addresses.

---

Legal Communication Emails

Use this field for recipients who should receive legal and compliance communications.

Maximum: 5 email addresses.

---

Security and Data Protection Contacts

Use this field for recipients who should receive notifications about:

• Security incidents
• Data protection issues

Maximum: 5 email addresses.

Recommended Practice

Use shared organizational addresses or designated responsible contacts where appropriate so important notifications remain available if an individual changes role.

Expected Outcome

Configured recipients receive the applicable AppNavi communications for their notification category.

---

Expected Outcome After Configuration

After saving a setting, the expected result depends on the feature being configured.

---

Authentication does not work after changing the settings

Verify:

• Client ID
• Client Secret, where applicable
• Authorization URI
• Token URI
• UserInfo URI
• Issuer URL
• Scopes
• Claim fields
• Redirect or callback configuration
• Identity Provider application configuration

For OIDC-specific troubleshooting, see End User Authentication.

---

Discovery does not show expected data

Check:

1. Enable App Discovery is enabled.
2. The correct data source is selected.
3. The selected discovery source is configured correctly.
4. The Discovery module is available.
5. The expected application activity has occurred.

Review App Discovery for the complete discovery workflow.

---

Related Documentation

Use the following documentation when you need detailed configuration beyond the tenant-level Settings page:

The Settings page should be treated as the starting point for tenant configuration, while feature-specific documentation should be used for detailed setup and troubleshooting.

---

Quick Reference

---

Summary

The Settings page provides tenant-level configuration for core AppNavi functionality.

Use it to:

• Configure general tenant behavior.
• Enable AI capabilities.
• Strengthen authentication and session security.
• Connect an Identity Provider.
• Configure SSO.
• Enable Guidance content import.
• Configure App Discovery.
• Manage notification contacts.

For each change, follow the same approach:

Identify the requirement → check prerequisites → configure the setting → save → validate the affected feature → review the related documentation.

For complex configurations such as OIDC, SSO, Discovery, or application behavior, use the linked feature-specific documentation rather than treating the Settings page alone as the complete configuration guide.