# Modules A module is like a **“snippets of cards or flows”** that you use often across different boards. You can create and save modules to reuse them instantly in other boards, without having to recreate them each time ### **How to Create a Module** You can create a module in two ways: **Method 1: Create a Module from a New Board** * Click **“Modules”** on the sidebar, then click **“Create”** to build a frequently used module that you can reuse in new boards
**Method 2: Create a Module from Existing Board Cards** * **Step 1:** Select the card or group of cards on your existing board. You can choose a single card or an entire connected flow that you want to convert into a module * **Step 2:** Start creating the module by selecting **“Module”** from the toolbar after making your selection
* **Step 3:** Enter the module name and a short description, then publish it for personal use or share it with your team
* **Step 4:** You can see all modules or choose to edit your own. When you edit a module, you will be taken to a dedicated editing board, which is a private space accessible only to you as the creator. Here, you can update the description, review the settings, and prepare the module for publishing
### **How to Find Your Modules** **Within a board (for use):** When working on any board, you can quickly access modules by looking for the module icon or menu. A sidebar or pop-up will display all available modules for use
**From the Home page (for editing):** To manage or edit the modules you have created, go to the **“Modules”** section on Aerogram’s Home page. This area displays all of your personal modules, where you can edit or publish them as needed
### **How to Use Modules** When working on any board, you can quickly access modules by looking for the module icon and clicking the module button
Then, click the **“Add Module”** button or drag and drop the module onto the board. The system will automatically create it for you, and it will be ready to use immediately
### **Module Permission Management** When you create a module, you can control how other users interact with each card by setting **card permissions**. These settings determine what users can see and edit * **Show All:** Users can view everything in the card (including prompts and outputs) and can edit the content * **Hide Prompt:** Users can run the card and view the output, but cannot see the original prompt * **Hide Prompt and Result:** Users can only run the card but cannot see either the original prompt or the output. This is suitable for hiding complex internal logic (black-box use)
**Module Viewer:** Users who can view and use the latest version of a module\ **Module Editor:** Users who can edit the module and publish new versions