Security and deployment
Your deployment and agreement determine available infrastructure, regions, providers, retention, and support procedures. Use the current Security overview, Privacy policy, Terms, and Subprocessors/DPA for published statements. This guide explains product controls; it does not establish a certification or contractual guarantee.
Deployment scope
Ennea's cloud application and a local Edge host have different responsibilities. The Edge host connects factory equipment to the cloud; it is not a complete offline or on-premise installation of Ennea. Dedicated hosting, customer-cloud, hybrid, or on-premise arrangements require an explicit agreed deployment profile. Do not infer their availability from a configuration example.
Before connecting a site, confirm application/API origins, data locations, storage and backup ownership, allowed network flows, external destinations, and the responsible operators. Test and Production must use the intended connections and permissions.
Identity and permissions
Named users authenticate with their own account and supported MFA. Organization membership, scoped grants/groups, resource restrictions, and current session state determine access. Shared terminals and service identities have separate provisioning. See Account security, Roles and permissions, and Device setup.
A visible page, proposal, or approval does not grant unlimited authority. Publishing definitions, approving actions, and applying changes are distinct. External agents act within their delegated access level and the user's current rights. They save shared drafts and publish or execute only through eligible explicit operations; native business approvals remain authoritative.
AI and external data flows
Konnie uses the configured provider profile and workload settings. Provider/model choices and file-processing settings are managed in the authorized Control Center views. Credentials are provisioned through the approved deployment/credential process; the Control Center reports their readiness. A deployment may offer different providers for different workloads. Confirm the chosen recipients and terms with your administrator before processing restricted material.
Files and connected messages are source evidence. Downloads, extraction, generated documents, sandbox work, conversation history, and external actions can have different storage and retention paths. Product access controls do not by themselves prove a provider's residency or retention contract. See Files and media and Control Center.
Responsibilities
| Owner | Responsibilities |
|---|---|
| Ennea/deployment operator | Agreed infrastructure, secret management, backups, monitoring, incident handling, release operations. |
| Customer administrator | Users/groups, scope, devices, published configuration, approved external connections. |
| Process owner/operator | Correct identifiers, quantities, units, review, actual operational outcome. |
| External-system owner | Source authority, credentials, mailbox/database restrictions, destination reconciliation. |
Verify backup/recovery targets and restoration evidence for the actual deployment. A local test or stored backup is not proof of a successful production restore. Retention, exports, deletion, and support access require the applicable operating procedure; Organization Options cards do not implement all of these controls.
For security concerns use the responsible administrator or security@ennea-ai.com, as listed in the Security overview. For DPA/privacy arrangements use the published Subprocessors/DPA contact. For operational failures see Support.