> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/on-premise/how-to-guide/configuration/applications.md).

# Applications

Add custom web applications to the Navixy main menu using SQL queries. Enable apps for entire service accounts or individual users, with HTTPS required.

In your Navixy instance, you can modify the list of web applications available to your users by adding or removing custom apps to the main menu.

{% hint style="info" %}
Standard modules, such as Field Service and Fleet Management, cannot be enabled or disabled in the database or in platform configuration files. Their presence in the interface is conditioned by the terms of your instance's tariff plan.
{% endhint %}

## Embedding custom applications to Navixy

The Navixy platform allows you to integrate your custom web application into the Navixy main application interface. This custom application will appear as a distinct item in the main menu, and upon clicking, it will open a specified external URL address as an internal interface application.

![On-Premise - Configuration - Applications](https://4021216648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkUnMmePH99SsdChtqqu7%2Fuploads%2Fgit-blob-1001145f56e870172c56e86ef80dd994f69759d4%2Fimage-20230810-133621.png?alt=media)

There are several parameters the integration can have:

* *%name –* application name
* *%link\_to\_the\_app –* link to the application

To activate an application and make it available for the entire service account or specific users, use the following SQL queries in the database.

**Enabling the app for the entire service account (all users)**

{% code overflow="wrap" %}

```sql
INSERT INTO google.plugins2dealers (dealer_id, plugin_id, parameters) VALUES (1, 52, '[{"name": "%name","app_page_url": "%link_to_the_app"}]');
```

{% endcode %}

Change the highlighted parameters in bold to match the name and link to your app.

**Enabling the app to individual user accounts**

{% code overflow="wrap" %}

```sql
INSERT INTO google.plugins2users (user_id, plugin_id, parameters) VALUES (%user_id, 52, '[{"name": "%name","app_page_url": "%link_to_the_app"}]');

```

{% endcode %}

In this case, replace %user\_id with the user ID that should have access to this app. If multiple users need access, each user will require their own command.

{% hint style="danger" %}
Note that if you are using an HTTPS connection, your app link must also be HTTPS to avoid a mixed content error. Once you have added the app successfully, it should appear in the Navixy platform menu.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/on-premise/on-premise/how-to-guide/configuration/applications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.