Platform operations
Clear controls for platform operations
The people who run the service are held to a higher bar.
Platform operators run DynamicForm from a separate console. Their sign-in, roles and company access have controls that support accountable service administration.
Separate service administration
Platform operators use a separate sign-in address and console, rather than signing in as company users.
Operators onboard companies, set their web addresses, issue mobile application keys, suspend companies and end their sessions. Working inside a company requires an audited session with a stated reason.
Company administrators continue to manage their own users, security and applications within platform policy. Explore Company Admin for the company's administration responsibilities.
Stronger operator sign-in
Every platform operator must use an authenticator app; this requirement cannot be switched off. Operator sign-in does not use SMS or email codes. Recovery codes cover a lost phone.
An operator can trust their own browser and use a PIN on it. Sensitive actions require a fresh PIN or authenticator code. These include acting inside a company, changing data stores and managing keys. The fresh check applies when the sensitive action is requested.
Roles for platform operators
Built-in roles include full administrator, support and read-only auditor. The console shows each operator only the sections their role permits, keeping their view aligned with their responsibilities.
An operator cannot grant more access than they hold. The last full administrator cannot be removed.
Limits across the service
Platform policy determines which data layers companies and applications may separate. Platform AI and Maps keys are offered only to companies allowed to use them.
The platform also sets product menus shared by every company. Application menus remain part of each application's design. Company roles and permissions determine what people can reach within that shared product structure.
Each published application's Android builds get their own keys; only the latest few stay active.
Watch service health
Follow service health from a live server monitor. Per-server cards show CPU and memory, alongside database, document store and cache health. The monitor also shows the health of each company's separate stores.
Review 24-hour history to understand recent changes. When a limit stays crossed for several minutes, the monitor raises an alert in the platform log.
In this section — Architecture
Explore DynamicForm — AI Core · Multi-company SaaS · Security and identity · Branding and app publishing · Company Admin · Applications
Updated 30 October 2026