> For the complete documentation index, see [llms.txt](https://docs.flightwatching.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flightwatching.com/user-manual/admin-user-manual/edit-plugins.md). # Edit Plugins WILCO works with the plug-ins (or plugin, add-in, addin, add-on, or addon), that is a software component that adds a specific features that enables customisation. In order to manage your plugins, click on *ADMIN* and then *Edit Plugins :*

At the top left corner there is a search box that permits you to search by for example: type of the aircraft/[FWOT type](/user-manual/admin-user-manual/general-conf/assets/fwot-types.md) to find the plugins that are related to that aircraft. The 'header' of visualisation shows the amount of plugins that could be manage on the platform and on the right side have two buttons: *Preview* and *CHECK UPGRADES:*

Clicking on the *CHECK UPGRADES* button permits to check throughout all the plugins if there were any changes done by any user. The information when was done last check is situated below each and every plugin. In example below, plugin *fw\.a220* Last check was 4 hours ago:

## list of plugins The *Edit Plugins* view shows the list of all the plugins installed on the platform - both editable and non-editable; with the local changes or the different VCS:

Let's focus on the above image. The plugins are displayed as a list. Each row contains from the left to the right: * the *name of the plugin* (this is the name set up at [General Conf](/user-manual/admin-user-manual/general-conf/configuration/plugins.md#add-plugin)) prefixed with the *icons*:

* the *airlines* that are set to be using the plugin or, if none - par default on all airlines:

* the *DET/DEL* buttons. *DET -* stands for *DETAILS;* while *DEL* is *DELETE* button. ## details of plugin Click on *DET* button to get to the details of any plugin. Let's take example of the following plugin:

Starting from the top - the header contains from the left to the right: * name of the *plugin* * *airlines* using it * *buttons* (ALL | RE-DEPOY | LOGS | OPEN | GITHUB) * ALL - permits to go back to display of all the plugins * RE-DEPLOY - removes the whole content of the plugin and replaces it with the lates VCS * LOGS - provides the list of LOGS * OPEN - shows up all the elements of the plugin (you can also use the '+' button situated in front of every element to see what it contains) . * GitHub - work in progress. Below the header, we have all the list of the elements previously explained, [plugin contains plenty of elements designed on the platform](/user-manual/admin-user-manual/general-conf/configuration/plugins.md). Taking example of the plugin on the image above. It contains: * *layouts* (ex: 17 layouts) * *fault codes* (ex: No faultCodes) * *parameters* (ex. 546 parameters) * *dashboards* (ex. 1 dashboard) * *trend bundles* (ex. 3 trendBundles) * *event table bundles* (ex. no eventTableBundles) * *bookmarks* (ex. No bookmarks) * *constants* (ex. 1 constant) * *docs* (ex. No docs) * *ifts* (ex. 8 ifts) * *elastic* *(big data)* (ex. No elastic) Any element could be accessed from here. For example, if we'd like to see what dashboards this plugin contains, we should click on the '+' sign situated prior to *1 dashboards.* It will open up the dashboard elements:

Each element (in this example: the dashboard) has a little icon on the bottom right of its display that after clicking takes us to the editor of that element: