Organise applications and their data

See the company's applications together, with Draft, Published and Retired statuses. 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.

Create a hand-built application with a code and a name. Use the register to review its status alongside the company's other applications. Retire a hand-built application when it is no longer needed.

People and roles remain at company level. Each application keeps its own screens, workflows, menus and work. The company theme library also stays shared, while each application picks its theme and carries its own logo.

Records, documents, files, logs and cache can stay in company stores or move into the application's own stores. Logs follow the application, and files remain in the company's or application's own file store.

Choose logical separation within a shared store or physical separation in an application's own database, including on another server. The platform operator sets which layers may be separated. Your company administrator chooses within that policy, including giving an application its own cache.

Move a layer when needed, or move it back to the company store. Only that application pauses during the maintenance window. My tasks and dashboards still gather the application's work across its stores.

Use your own AI provider keys for your company's work. Company keys serve only your company and are never shared with another company. The keys panel shows whether keys are set without showing their values.

Platform keys are available only where the platform allows your company to use them. If a company AI key is wrong, the call fails rather than silently switching. Each AI call records whose key it used, so the source of access stays clear.

Add Google Maps keys for web and Android in the same company panel. They follow the same company and platform access rules. Without a Maps key, people see coordinates and a map link.

Maintain an integration definition once for the company, then choose which applications may use it. Designers see only integrations within their application's scope.

The scope cannot be removed while the integration is in use. API clients have their own chosen application scope, limiting the applications that calling systems can reach.

Shared definitions do not make application designs shared. Each screen, workflow and report belongs to an application. Use the company library when you want to copy a design into another application, with its linked items reviewed first.

In this section — Integrations

Explore DynamicForm — AI Core · Multi-company SaaS · Security and identity · Branding and app publishing · Company Admin · Applications