Questions about applications

Every company has a Main application. AI Core adds an application for each blueprint it builds. It shows as Draft until it is published. Company administrators can create hand-built applications.

Sign in at your company's address. Your only application opens directly; several applications appear on a dashboard. Tiles show logos or coloured initials, waiting tasks and Draft status where applicable. The header switcher moves between applications and shared areas, and remembers your last application.

Application access comes from roles through menus, workflow steps or design functions. End users see only applications their roles reach. Company administrators see all applications.

The company keeps sign-in, users, reporting lines, branches, holidays, roles and Company administration. Integration definitions, scoped API clients, company settings, OTP settings and the theme library also stay shared. Applications keep their own designs, records, identity, logs and any separate stores.

Yes. Each application chooses a theme from the company theme library and carries its own logo. The whole web app takes the open application's colours and logo. Each application also has its own branded Android app and application key.

The inbox shows the open application's work. My tasks and the case monitor follow that application too. Inbox work loads in pages to stay responsive as case volumes grow. Application task lists still gather work across the stores used by that application.

Yes. Browse the company library for screens, workflows, master lists, reports and dashboards. Review the copy plan and its linked items. Link to the target's item with the same code, or copy it. The copy belongs to the target application and remembers its source.

No. Codes need to be unique only within an application. A screen, workflow or report belongs to its application. The copy plan shows linked items for review. Choose whether to link within the target application or copy those items.

Yes, within platform policy. Records, documents, files, logs and cache can use company stores or separate application stores. Separation can be logical or physical, including on another server. Move layers when needed; only that application pauses, and its logs follow it.

Define an integration once for the company, then choose which applications may use it. Designers see only in-scope integrations. Scope cannot be removed while the integration is in use. Calling systems reach only the applications selected for their API client.