Applications
Keep work inside its application
Move between applications while keeping their designs, records and connections in the right place.
Each company starts with Main and can create hand-built applications. AI Core adds an application for each blueprint it builds. It shows as Draft until it is published.
Start at your company
Sign in at your company's address. An application opens directly when it is your only application. With several, the application dashboard helps you choose. Tiles show the application's logo or coloured initials, waiting tasks and Draft status where applicable.
Use the header switcher to move between applications, return to the dashboard or open Company administration. DynamicForm remembers your last application. Your roles determine which applications you reach through menus, workflow steps or design functions. Company administrators see all applications.
The whole web app adopts the open application's theme and logo. My tasks, the inbox and the case monitor follow that application. The inbox loads pages of work, keeping large case volumes manageable.
Review before reusing
Screens, workflows and reports do not stay shared across applications. Their codes need to be unique only within their application.
Open the company library to browse screens, workflows, master lists, reports and dashboards from other applications in your company. Select an item and review the copy plan. The plan shows the linked items that come with it.
Join a linked item to the target application's item with the same code, or copy it into the target. The resulting copy remembers where it came from.
Place each data layer
Choose stores for records, documents, files, logs and cache within platform policy. An application can use company stores or its own stores. Logical separation keeps it separate within a shared store. Physical separation gives it its own database, which may sit on another server.
Move a layer whenever needed, including back to the company store. Give an application its own cache when that is the required arrangement. Only the affected application pauses during the maintenance window, and logs follow the application.
My tasks and dashboards still gather that application's work across stores. The company administrator chooses the arrangement within the layers the platform permits.
Choose permitted connections
Set up each integration definition once for the company. Its application scope determines which applications can use it. Designer pick lists show only integrations within the open application's scope, keeping unavailable connections out of that selection.
Review where an integration is used before changing scope. DynamicForm prevents scope removal while the integration remains in use.
API clients also have application scope. A calling system reaches only the applications selected for its client.
Let roles span applications
Give a role menus in the applications it needs. The role page brings Permissions, Application access and Data scope together. Application tabs show menu choices separately, while the role remains part of the shared company organisation.
For example, a role may reach both Employee Leave and Purchase Requests.
In this section — Integrations · Questions
Explore DynamicForm — AI Core · Multi-company SaaS · Security and identity · Branding and app publishing · Company Admin · Applications
Updated 30 October 2026