--- title: "Field and Module Tags" slug: "tags" updated: 2025-12-23T15:50:07Z published: 2025-12-23T15:50:07Z canonical: "docs.unqork.io/tags" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Field and Module Tags **Tags** are used in Unqork to organize and group modules or components based on their function. There are two types of tags you can use when building in Unqork: **module tags** and **field tags**. The tags you use and how you use them enable you to take advantage of Unqork tools or target multiple components at once using logic components. ### Module Tags Module tags highlight the function of a specific module. Using module tags lets everyone with access to an application view which modules are used for APIs, schemas, or other functions. Even if a team member is unfamiliar with that module, tags can provide them with context and help improve application maintenance. In addition to following application maintenance best practices, module tags are also used to add modules to certain [UDLC Tools](/v1/docs/udlc). Adding the `api` tag to a module connects it to the [API Docs Dashboard tool](/v1/docs/api-docs-dashboard-tool), while the `schema` tag makes that module available to view in the [Schema Docs Dashboard tool](/v1/docs/schema-docs-dashboard-tool). #### Accessing Module Tags in the Module Builder To add a tag to a module, enter the desired tag in the **Tag** field when creating a module. If you select the **API** Module Type, the `api` tag is added automatically. Module tags can be viewed or edited from either the Module or Application page. To view and edit a module tag from the Module Builder: 1. Open your module in the Module Builder. 2. At the top right of the Module Builder, click the ![ellipsisButtonDummy.jpg](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/ellipsisButtonDummy.jpg?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A04Z&se=2026-11-08T11%3A18%3A04Z&sr=c&sp=r&sig=5FN50KibULZvs%2Bsml1U%2BOmiNSPzTfIY1Qzjr4vf6wcE%3D) **(ellipsis)**. 3. Select **Module Settings**. 4. In the **Tags** field, view or edit the available tags. 5. Click **Save & Close**. ![Module settings with the Tags field highlighted.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/API Tag.png?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A04Z&se=2026-11-08T11%3A18%3A04Z&sr=c&sp=r&sig=5FN50KibULZvs%2Bsml1U%2BOmiNSPzTfIY1Qzjr4vf6wcE%3D) #### Accessing Module Tags in an Application To access module tags from the Application page: 1. On the application page, locate your module. 2. At the top right of the page, click the ![ellipsisButtonDummy.jpg](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/ellipsisButtonDummy.jpg?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A04Z&se=2026-11-08T11%3A18%3A04Z&sr=c&sp=r&sig=5FN50KibULZvs%2Bsml1U%2BOmiNSPzTfIY1Qzjr4vf6wcE%3D) **(ellipsis)**. 3. Select **Settings**. 4. In the **Tags** field, view or edit the available tags. 5. Click **Save & Close**. ![Module Details pop-up with Tags field highlighted.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Application API Tag.png?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A04Z&se=2026-11-08T11%3A18%3A04Z&sr=c&sp=r&sig=5FN50KibULZvs%2Bsml1U%2BOmiNSPzTfIY1Qzjr4vf6wcE%3D) #### Extension Tags Modules can also be converted into an extension module using the `extension` tag. Extension modules display in the [Extensions drawer](/v1/docs/module-extensions) for all Creators in the environment. > RBAC for Extensions is not supported at this time. The size of an Extension’s modal can be controlled by adding a size tag to the module. For example, to create a medium-sized Extension modal, you can assign the module the `extension` and `size:-medium` tags. The available size options include: - `size:-small` - `size:-medium` - `size:-large` - `size:-xlarge` ### Component Field Tags Every Unqork component has a **Field Tags** setting. Field tags are commonly used in API modules to organize [Hidden](/v1/docs/hidden-component) components containing parameters by data type. In addition to organizing and grouping components, field tags let you target grouped fields using logic components. ![Hidden component settings with the Field Tag highlighted.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image-1765817763879.png?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A04Z&se=2026-11-08T11%3A18%3A04Z&sr=c&sp=r&sig=5FN50KibULZvs%2Bsml1U%2BOmiNSPzTfIY1Qzjr4vf6wcE%3D) #### Using Field Tags in API Modules When building an API module, it’s a best practice to set the data type for each parameter using field tags. The component comes preset with all available tags. Delete all tags that you do not want to apply. The available tags are: - `type:string`: If the data type is an alphanumeric string. - `type:number`: If the data type is an integer or a floating-point number. - `type:boolean`: If the data type is Boolean (true or false). - `type:array-string`: If the data structure is an array containing a string data type. - `type:array-boolean`: If the data structure is an array containing a Boolean (true or false) data type. - `type:array-number`: If the data structure is an array containing an integer or a floating-point number data type. - `type:object`: If the data structure is an object. - `type:ObjectId`: If the data is a MongoDB unique identifier. > [!NOTE] > The `type:array` tag is the same as the `type:array-string` tag. #### Using Field Tags in Logic Components Field tags can be added to logic components to affect all components with that tag simultaneously. Doing so lets you apply logic to several components without listing each one individually in the logic component. To use field tags with logic components, add the desired field tag to each component. In your logic component, add the field tag to the **Property ID** column of the **Outputs** table. The logic function set in the component now outputs to all components with that tag. In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. Schema is a declarative language that defines the structure, content, and constraints of the data. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network. A modal is a window that appears on top of the content you are currently viewing. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. Data types are a classification of data that determines how it is stored and interpreted. A string is an object that represents a sequence of characters. Strings typically hold data represented in text form. The Boolean data type accepts one of two values: true, or, false. An array is a type of object that stores one or more data types. Data types supported in arrays include numbers, strings, and objects. An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.