> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/xoops-operations-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/xoops-operations-guide/the-admin-interface/modules/setting-module-visibility-and-menu-order.md).

# Setting module visibility and menu order

![img\_91.jpg](/files/-LD6N0WFSnGOs83Tn5bh)

Figure 18 Module Activation and Main menu visibility

The modules administration table has headings for: Module, Version, Last Update, Active, and Action.

This page gives you options to ‘Activate’ the module in your website or keep it installed but hidden from any menus or interaction. You can also deactivate the module from this page (or uninstall altogether, as we will describe later.)

The green “checkmarks” in the 'Active’ and “Menu” columns indicated that the module is active in your website and admin section and also visible in your menu systems. Remember, you still need to select in which pages, position and groups the module will appear in. By clicking on the green checkmark will change the status to “deactivated” indicated by the “off” icon.

The same is for “Menu”. But changing the status to “off” will keep the module active, but prevent any links appearing in the page menu systems. This is useful if you utilize custom menus or links to display pages.

![img\_92.jpg](/files/-LD6N0WI_vswzqzDL9Ix)\
Figure 19 Deactivated module.

You can also change the order of the modules in the menu by simply dragging them up or down. As soon as you drop the module, the new order will be reflected in the Menu. Here we’re dragging the “User Profile” to be above “Private Messaging” and the change is reflected right away in the Menu:

![img\_93.jpg](/files/-LD6N0WK5COzkzsV2eRr)

**Deactivating and uninstalling a module**

While we are still in the module administration page, let’s complete the options here by describing how to deactivate and uninstall a module.

* Looking at the table at the top of this page, you will see a list of your registered modules. ![img\_95.jpg](/files/-LD6N0WM1dz4Q8RNTf1e)  
* Click on the Un-install Icon:   
* You’ll go to a confirmation page:

  ![img\_96.jpg](/files/-LD6N0WOdIMspKTgtGM-)
* Just press ‘Unistall” button to confirm.
* You'll see a page with the changes just made. What happens is the module has been now been deactivated and disconnected from the XOOPS' system. However the physical files still reside on the server in the modules directory where you uploaded them. Click on ‘Back to module administration’ page
* The module you just uninstalled won't be on the registered modules list at the top of the page, but now at the bottom of the page, among the modules that are available in XOOPS' modules directory but haven't been installed. You are now back where you started after initially uploading the module.

**Note:** *Uninstalling a module deletes all content associated with that module - the tables defined by the module are dropped, and all blocks, templates, configuration options, comments, notifications, etc. associated with the module are removed from the database. Now the module is disconnected from the XOOPS core, if you wish to do so, you may safely delete the module files on the server manually.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://xoops.gitbook.io/xoops-operations-guide/the-admin-interface/modules/setting-module-visibility-and-menu-order.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.