Apps
An app can be either a web app (accessed via a URL) or a desktop app (installed on the desktop).
For any app, you can configure a large number of settings to customize users' experience with it. While many of these settings are optional, the most important ones are grouped under Basics and Access.
Categories of settings include the following:
-
Content Type: Select either Web App for items that are accessed on the web, or Desktop App for items that are installed on the desktop.
-
Basics: Core details about the app, such as the title and location.
-
Access: Rules specifying which users or groups can view or interact with the app.
-
Interop Settings: Definitions for intents (signals) that this app can perform.
-
Additional content controls: Settings to enable certain app features.
-
Browser control settings: Settings to disable backward, forward, and refresh buttons while using this app.
-
Redirects: Settings for managing how users are redirected to web-based apps.
The interfaces for adding and editing apps show the same settings, enabling you to manage existing apps or configure new apps consistently.
Categories of app settings
Select Content Type
The default is Web App. If you are configuring an application that is installed on the desktop, select Desktop App instead. The fields in the Basics section vary depending on the content type you select.
Basics
The Basics section is where you configure the key settings for an app in the HERE platform. This section helps define the app's primary information, such as its location and display name, as well as configuration options for enhanced access.
Web App basics fields
-
In the URL field, enter the main URL where users are to be directed when they click on the app. This is the primary link that the item points to. Ensure the URL starts with the correct protocol (
https://
orhttp://
). -
In some cases, an app may require access to additional domains, such as region-based forwarding or domains required for authentication. Click Add Allowed URL to add more URL fields.
-
The system automatically generates a list of patterns of accessible URLs based on the entered domains, including wildcards for subdomains and paths.
-
If you add a URL field you don't need, click the trash can icon to delete it.
-
Desktop App basics fields
-
In the Path or Scheme field, you can enter either a file path or a custom scheme for the application.
-
Click + Argument to enter any command-line arguments that you want to be passed to the application.
Shared basics fields
-
Enter the name of the application in the Name field. For web apps, the system automatically populates the Name field based on the title of the web page at the first listed URL; you can edit it if you want a different name. For desktop apps, you must enter the name manually. The name is displayed for the app in the HERE platform. Choose a name that is descriptive and easily identifiable by users.
-
Enter an identifier for the application in the ID field. For web apps, the system automatically populates it based on the title of the web page at the first listed URL; you can edit it if you want a different ID. For desktop apps, you must enter the ID manually. The ID must be a unique identifier across all apps, as it is used internally. As a best practice, use a standardized format for IDs, such as lowercase, hyphen-separated.
-
(Optional) You can add a custom label to the app. This label is typically used for internal reference purposes, such as auditing or cataloging, and can include any relevant information that helps track the app.
-
Click Add Custom Label to add a Custom Label field.
-
If you add a Custom Label field by mistake, click Remove to remove it from the page.
-
-
(Optional) Choose an icon to help visually identify the app. For many apps, the system automatically populates the Icon field. If it doesn't populate, or if you want to change it, you can upload an image file for the icon representing the app. Image files for icons must be in JPG or PNG format and must not exceed 1MB in size.
-
(Optional) Select the Featured Content checkbox to mark the app as featured. Featured content appears prominently in new tabs for users who have access to it. As a best practice, mark only the most relevant apps as featured content, to ensure that these items stand out to users.
-
(Optional, for web apps only) Select the Allow HERE API Access checkbox if a web app requires access to the HERE API. This setting is essential for applications that need to integrate with the platform's API services.
Access
The Access section defines which users or groups are permitted to view and interact with the app. Only the specified groups and users listed here have access to the app. This section is critical for ensuring that only authorized users or groups can view or interact with the apps in the platform. It allows for precise control over access permissions.
-
Click Grant Users Access to add individual users or groups that should be able to access the content.
-
Use the search field to filter users and groups by name.
-
In the All listbox, select the checkbox next to the ID of any users or groups you want to have access to the app. Selected users and groups are listed in the Selected listbox.
-
When you have selected exactly the users and groups you want to access this app, click Grant Access.
Interop Settings
Starting in HERE 9, the Interop Settings section defines the intents (or workflow signals) that an app can perform. You provide intent definitions via a JSON file, either via URL or by uploading it.
To add intent definitions:
- Click Update. The Add Intent(s) dialog box opens.
- Enter a URL in the URL field, or click Upload File to browse for a file on your computer. In either case, the file must follow the format described below.
- Click Add to add the definitions to the app.
The format of the intent definitions file is the following:
"interop": {
"intents": {
"listensFor": {
"INTENT_NAME": {
"displayName": "USER-FRIENDLY NAME",
"contexts": [
"CONTEXT-1",
...
"CONTEXT-N"
]
},
...
}
}
}
The following is an example of an intents definition file:
"interop": {
"intents": {
"listensFor": {
"StartChat": {
"displayName": "Start Chat",
"contexts": [
"Contact",
"ContactList"
]
},
"ViewChat": {
"displayName": "View Chat",
"contexts": [
"ChatRoom",
"Contact",
"ContactList"
]
}
}
}
}
This example defines intents for an app that can handle chats two ways: it can start chats for one or more contacts and it can view chats for contacts or a chatroom.
Additional Content Controls
The Additional Content Controls allow you to define how the browser should behave when displaying this app. These content control settings help ensure that data displayed in the HERE browser is managed and secured according to your organization’s policies, protecting sensitive information from being copied or shared outside the designated environment. These features can be used as part of an organization's broader strategy for data loss prevention (DLP).
These settings apply only to web apps. They are ignored for desktop apps.
The following options are available:
-
AI Participation: In AI Center, when a user sends a Context prompt to their AI model, approved and currently viewed content is extracted and sent as context attached to the prompt. When enabled, users can send content from this app to the AI model. When disabled, content from this app is excluded from being sent to the AI model.
-
Copy Protection: This option prevents users from copying any content from the application or website. Toggle the switch to turn this feature on or off. When this option is turned on, users cannot use copy commands (for example, Ctrl + C or right-click copy) and cannot drag the content to drop it onto another application.
-
Secure Copy: When this option is enabled, users can paste copied data only into other applications or websites within the HERE browser that have Secure Clipboard turned on. This ensures that copied data remains within the controlled environment of the HERE platform. Toggle the switch to turn this feature on or off. When Copy Protection is turned on, this option is turned off and disabled.
-
Secure Clipboard: This option prevents the app from accessing or reading data stored in the secure clipboard (via paste), further securing sensitive information from being shared unintentionally. Toggle the switch to turn this feature on or off.
-
Print Protection: This option prevents content of the app from being printed. When it is turned on, the Print context menu is disabled, and other ways of printing do not produce output.
-
Screen Share Protection: This option prevents the app from being captured via a screenshot or screen-sharing application. In the screen capture, on Microsoft Windows, the containing window appears black; on macOS, the window is invisible. This option operates at the window level, even if the protected app is in only one tab or supertab.
-
Simplified Window: When this option is turned on, this app always launches in a new window with simplified window controls.
Browser Control Settings
These settings determine whether typical browser controls are available when running this app:
- Disable Backward and Forward buttons
- Disable Refresh button
Redirects
For some web apps, you might want certain users to be sent to a different domain or URL when they attempt to access the app. Redirects offer flexible content routing, enabling different user groups to access customized content based on their needs.
Redirects are not relevant for desktop apps.
The Redirects section enables you to define these alternative destinations for users or groups. You can also assign a custom logo for clarity.
Add a Redirect
-
Click Create New Redirect. The Create Redirect dialog opens.
-
In the Name field, provide a unique name to easily identify the redirect. This could represent a department, region, or specific group of users that the redirect is intended for.
-
Enter a Description to provide additional context for the redirect. This can help other admins understand the purpose of the redirect or the specific circumstances for its use.
-
Click Redirect Options. The Redirect Options view opens, which is similar to the Basics section.
-
In the URL field, enter the main URL where users will be redirected when they click the app. This is the primary destination for the redirect. Ensure the URL starts with the correct protocol (
https://
orhttp://
). -
In some cases, apps might require access to additional domains, such as region-based forwarding or domains required for authentication. Click Add Domain to add more URL fields. The system automatically generates a list of patterns of accessible URLs based on the entered domains, including wildcards for subdomains and paths.
- If you add a URL field you don't need, click the trash can icon next to it to delete it.
-
-
In the Name field, provide a unique name to easily identify the redirect.
-
(Optional) For many web apps, the system automatically populates the Icon field based on the favicon associated with the URL. The icon helps visually identify the content. If it doesn't populate, or if you want to change it, you can upload an image file for the icon representing the content item. Image files for icons must be in JPG or PNG format and must not exceed 1 MB in size.
-
Click Select Users to specify which users or groups are to be redirected to the new URL:
-
Use the search bar to find users or groups by name.
-
Select the checkbox for users or groups that should be associated with this redirect.
-
-
When you've finished configuring the redirect, click Define Redirect.
Once a redirect is created, it appears in the Redirects table with the following information:
-
Redirect Name: The unique identifier you provided for the redirect.
-
Number of Users: This column shows how many users or groups are currently associated with this redirect.
-
Date Created: The date when the redirect was originally added.
Edit a redirect
-
Locate the redirect you want to edit, using the search bar to filter the list if needed.
-
Click the Action ⋮ menu on the right end of the redirect's row.
-
Select Edit.
-
Modify the redirect settings.
-
Click Apply to save the changes.
Delete a redirect
-
Locate the redirect you want to edit, using the search bar to filter the list if needed.
-
Click the Action ⋮ menu on the right end of the redirect's row.
-
Select Delete. The redirect is immediately deleted.