Infrastructure Modules

Infrastructure modules are standard Unqork modules assigned to four special roles in an application: header, footer, login, and logout. Unlike the content modules that make up an application's screens, infrastructure modules provide structural and authentication behavior that applies across the entire application.

Infrastructure modules are assigned in Application Settings or when Creating Applications.

Header Module

The header module renders at the top of the application and persists across all module navigations. When an end-user moves between modules, the header remains loaded. It does not reload on every navigation.

The header module renders as a standard Unqork module. Any component that works in a regular module works in the header. Common uses include navigation menus, branding, and end-user context displays.

Behavior:

• Loads once at application launch and remains in place for the full session.
• Renders above the active content module on every screen.
• Can be previewed with the application's header and footer from the Explorer. Select the (ellipsis) menu on a module and choose View in Express ▸ View in App. This option is available for UI and standard modules, not API modules.

Footer Module

The footer module renders at the bottom of the application and behaves identically to the header module. It loads once and persists across all module navigations.

Common uses include support links, legal text, and secondary navigation.

Behavior:

• Loads once at application launch and remains in place for the full session.
• Renders below the active content module on every screen.

Login Module

The login module handles end-user authentication. When an unauthenticated end-user attempts to access the application, the platform checks whether a login module is assigned. If one is, the end-user is redirected to the login module instead of the platform's default authentication screen.

The login module renders standalone. The header and footer modules are not displayed while the login module is active. This lets Creators design a focused authentication experience without the application chrome.

Behavior:

• Renders when an end-user is not authenticated and attempts to access the application.
• Header and footer modules are not rendered while the login module is active.
• Once the end-user authenticates successfully, the platform redirects them to their intended destination in the application.

Building a login module: The login module is a standard Unqork module. Use components like Text Field, Button, and Plug-In to collect credentials and call the appropriate authentication service. The platform handles session management. The module must authentication.

Logout Module

The logout module renders after the platform clears the end-user's session. When an end-user logs out, the platform ends the session and then loads the logout module if one is assigned.

Common uses include a confirmation screen, a redirect to a marketing page, or a prompt to log in again.

Behavior:

• Renders after the platform clears the end-user's session.
• The session check that would normally redirect unauthenticated end-users to the login module is suppressed while the logout module is active.

Assigning Infrastructure Modules

Infrastructure modules are assigned per application. The available modules are the following:

• Any module that belongs to the application.
• Library modules shared at the environment level.
• Library modules in workspaces the Creator can access.

To assign or update infrastructure modules:

1. In the Explorer panel, select the (ellipsis) > Settings next to the application.
2. Under Advanced Settings, select the module for each role from the drop-down.
3. Select Save Changes.

Infrastructure modules can also be assigned in the Infrastructure Modules section of the Create Application form.

Limitations

• Each role accepts a single module. An application can have at most one header, one footer, one login, and one logout module.
• Infrastructure modules are not version-locked independently. When an application version is created, the header and footer module assignments at that point are captured. Login and logout modules are not versioned with the application.
• Custom Express login pages are not compatible with MFA. See Multi-Factor Authentication (MFA) for details.