# Module Overview A module is what we could consider an application within your instance. A module directly contains a set of blocs. Where pages are useful for building the navigation and sitemap of an instance, a module is useful for sorting out different applications within your instance. For example, you might have a CRM module, or Production Process module. ![A module with 2 sections containing 5 blocs](/files/-M_6pdKhXo7XkR97SCrz) {% hint style="info" %} **Note:** Pages and Modules look similar on the front end from a user perspective. For smaller instances a module simply directly loading from the home page might suffice, there may no need for multiples to contain modules. {% endhint %} ## Modules Interacting with each other Although modules are designed as a way to seperate your different applications, modules can also work together. All fields and rules in every module contain the ability to access data in any other module. This means you could have an entire network of modules all working together to perform tasks. For example, you might have a module called "Supplier & Customers", and another module for generating invoices, in the second module can access data like a customer list in the first module. --- # Agent Instructions: 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: ``` GET https://manual.blocworx.com/blocworx-documentation/module/module-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.