External agents and delegated access

Connect your own assistant to Ennea and decide what that connection may do. Confirmation stays between you and your agent. Ennea enforces the connection's access, your current permissions, native business rules, versions and history. There is no separate acceptance queue for each external-agent action.

Three access levels

Access	What the agent can do
Read	Inspect permitted records, configuration and drafts.
Draft editor	Read, create and edit ordinary shared Studio drafts.
Publisher	Edit drafts, explicitly publish saved revisions, and execute operational commands without a natural draft.

A connection remains limited to your selected workspace, environment and entity types. It cannot gain rights you do not currently hold. Revoke unused connections at any time; revocation stops future access and does not undo completed work.

Saving a draft never publishes it, including for a publisher. Drafts appear in the normal workspace where you and your agent edit the same content. Publication is an explicit operation against the exact saved revision. Concurrent edits cause a version conflict; the agent must read the current draft before continuing.

Connect

Install the supported Ennea plugin and use its browser sign-in/consent flow. Choose the workspace, access level and permitted record types. Discover current context and capabilities before starting: exposed domains are narrower than the complete browser or Konnie tool set. Tool arguments cannot change the connection's workspace or expand its authority.

Manage connections in Operations Studio → Integrations → AI agents → Agent access. Developer CLI credentials use the same access levels and entity scope. Choose their duration; the issuing login session can limit expiry further. Hosted OAuth connections show their expiry during consent and remain subject to your login session and current rights.

Store CLI credentials in the execution environment or a private credential file. Never place tokens in prompts, source documents or operation data. The supported plugin manages OAuth credentials through its host.

Edit and publish

Ask your agent for an outcome and supply the source data and known identifiers. It should preserve missing quantities, units and identities, inspect existing records and use the schemas returned by capability discovery.

For Studio configuration, ennea_read_draft returns the ordinary shared draft and its current authoring version. ennea_edit_draft saves a new draft revision with history. ennea_publish_draft explicitly publishes the exact saved revision when the connection has publisher access and you have the native publication permission. CLI equivalents are draft read, draft edit and draft publish with structured JSON input.

Materials, bills of materials and routings use the same saved manufacturing drafts that you edit with Konnie and in Operations Studio. Their existing revision history, attachment permissions and publication rules apply. A new Material remains unavailable to operational workflows until publication. The dedicated ennea_read_manufacturing_draft, ennea_save_manufacturing_draft and ennea_publish_manufacturing_draft tools use these same drafts. Their CLI form is draft read|save|publish material|bom|routing --stdin. Standalone Forms are not supported by these direct draft operations; use an App with its own inputs for a new form workflow.

For custom React Apps, ennea_edit_app or CLI app edit saves source, settings and connections directly as a shared draft. Read appProgram source first and retain its exact combined expectedVersion; unlisted files and settings remain intact. ennea_publish_app or CLI app publish is a separate explicit action. No implementation plan, staged change or acceptance task is created.

For example: “Update this inspection App as a draft; I will publish it later.” A draft editor can complete that work without publication rights. A publisher can also save the draft first and publish it only when explicitly instructed.

Operational commands and batches

Stock movements, production reporting and other operational actions have no natural authoring draft. A publisher connection can execute them directly through ennea_execute_command or CLI command execute, using the exact action and input schema from capabilities. Required native approvals, validation and provider execution still apply; an accepted command may report native work as pending.

ennea_execute_changes or CLI operations execute accepts a batch of native create/update/delete operations. Configuration edits with natural drafts save drafts only; explicit publication remains separate. Live records and commands without drafts require publisher access. CLI create, update and delete submit individual operations; changes execute is a compatibility spelling for the same direct batch flow.

Batches are not atomic transactions. Inspect every result and preserve exact versions, source identities, quantities and units. No prepare, stage, accept or apply steps are needed for external agents. Older proposal history remains available for inspection through the developer CLI.

Results and recovery

Keep the returned operationId, invocationId and idempotencyKey for the same intended request. ennea_operation_status or CLI operations status ID reads the durable outcome without repeating writes. Batch results are paginated: follow nextOffset until null and inspect each child operationId for native details. Counts describe the complete batch. Reusing the same request identity with identical input observes the same attempt. Do not select a new key merely because a response was lost.

Running, failed, partial and unknown results are not completion. Read native receipts and the resulting records before claiming success. Native receipts may report pending business approval or provider work separately from command execution. If an outcome is unknown, inspect it before making another attempt.

Factory Calendar commands have target and horizon limits; calendar configuration does not schedule production orders. Discover studioVersion for published/draft history and bounded diffs, and warehouse / materialFlow for native stock and movement workflows.

This external-agent connection is separate from Konnie's conversation governance. See Permissions, Publishing and Audit.

Follow Connect an external agent for plugin installation and a complete read-only CLI check with downloadable JSON input.