> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/modules/create-module.md).
# Create module
FlowScript modules contain reusable FlowScript functions, types, and values that can be shared across applications. For example, a module can be used to create functions and types for a specific service or to extend the functionality available in FlowScript in general.
Modules can be created inside an application package or in the application library. Modules inside a package can be used in all applications in the same package but are not visible to applications in other packages. \
Modules in the application library can be shared across all applications within the organization.
To create a new global module that can be utilized by all your applications, navigate to the application library, click the plus button in the **Assets** section, and select **FlowScript Module**.
Enter the name, description and a color of the module.
{% hint style="info" %}
Module names follow the same rules as FlowScript variables. They can contain alphabetical letters, underscores or numbers, but cannot begin with a number.
{% 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://docs.novacura.com/flow-connect/working-with-connect/create-and-design/modules/create-module.md?ask=&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.
