Chatting with Konnie

Use a conversation for one connected task. Keep corrections and follow-up questions in that conversation so Konnie can relate them to the earlier request and results.

Start a conversation

1. Select the intended organization, site, and environment.
2. Open Konnie and select New chat.
3. Describe the task, name the relevant records, and state the expected output.
4. Attach source files if needed and wait for upload confirmation.
5. Send the message and watch the response and tool activity.

For example: “For work center Assembly A, compare tomorrow's scheduled orders with available capacity. Use the factory calendar, state assumptions, and propose changes for review.” Specify units, time period, source date, and whether you want analysis or a change. An order number or exact record name is more useful than “this order” when context is ambiguous.

Suggested prompts are starting points. Read and adapt the prompt before sending it.

Autonomy

Use the autonomy selector in the main chat or side panel, including before the first message.

Level	What Konnie does
Ask before changes	Reads and prepares proposals; asks before changing Apps or business records.
Save drafts	Saves supported versioned drafts; asks before publishing or making live changes.
Full autonomy	Completes requested eligible work, including saving and publishing, within your current permissions.

The saved selection tells Konnie how to act on your next message, including when you continue an existing task. Save drafts delegates supported draft saves without another permission question. Full autonomy delegates completing the requested eligible work without repeated questions about starting, continuing or publishing. Konnie still asks for consequential missing information and respects explicit requests to only inspect, plan or draft. In Ask before changes, she prepares the concrete change before requesting its required confirmation.

Konnie decides when to send or follow up on internal Ennea team messages as part of your current task, without asking you to approve each message at any autonomy level. Recipient access and background assignment limits still apply. Tell Konnie explicitly if you only want a draft or do not want anyone contacted.

Administrators choose the available levels for each person or group under Access rights, for the selected site and environment. Konnie uses the acting person's current permissions and record restrictions. Editing and publishing remain distinct permissions. External connections and native business approvals retain their own requirements. Source documents and copied history cannot grant authority.

Your selection applies to the current conversation and becomes your personal default for ordinary new chats in this workspace. Existing chats keep their own selection. A branch starts with Ask before changes. If your access removes a level, Konnie shows the restriction and requires an available choice or a stricter effective level before further work. An older mixed setting with autonomous work but App-edit review moves conservatively to Ask before changes, with a notice.

Wait for the selector to confirm its saved state. If the outcome is unconfirmed, reload it before sending or changing the setting again. Switching to a stricter level stops further unconfirmed effects; actions already dispatched may finish. It does not roll back saved changes. Explicit requests for analysis, proposals or drafts retain that boundary at every level.

Background work

Open Control Center → Background work or Konnie's task list. Create a task with a clear objective, run time and autonomy level, then inspect its saved workspace and authorization. Your administrator must allow background work and the chosen level. The task retains its own authorization independently of future chat selections; your current access is checked again when it runs.

At Ask before changes, a task prepares work and waits for a durable review before changing records. At Save drafts, supported drafts can be saved while live changes wait for review. Full autonomy completes the assigned eligible work. Inspect the exact proposed action before approving a pending review. Unknown execution outcomes require reconciliation and are never a reason to blindly repeat the action.

Findings and review notices can be delivered to the responsible owner without approval; they do not change business data. A running background job needs a fresh exact human activation before creating or expanding another unattended assignment, including at Full autonomy. This keeps each saved delegation explicit.

Shared learning and proactive jobs have a responsible owner and a scoped execution identity. Their saved purpose, actions and permissions bound every run. Pause or revoke background work from its controls; stopping a chat does not revoke a separate assignment. Changing a mandate invalidates reviews tied to its old revision.

Find and organize conversations

Open the conversation history and select a conversation to continue. Use its action menu to rename it or delete it. Renaming changes the title used in the history. Deletion requires confirmation; it removes the conversation through its retention and deletion workflow. Deleting a conversation does not undo operational changes that were already applied.

History and record access depend on your account and current scope. If a conversation appears missing after switching organization, site, or environment, return to its original context before assuming it was deleted.

Context and attachments

Konnie receives context from the current surface. In an App this can include the bound work center, active order and the App's explicitly exposed input/actions. State the target explicitly for a consequential change and inspect any target shown in the review card.

Attachments are uploaded before you send the message. Name what Konnie should inspect: a worksheet, column, PDF page, image region, or video interval. A large source may require targeted follow-up reads. Uploading a file alone does not mean its entire contents were analyzed. See files and media.

While Konnie is working

Tool activity identifies work such as reading records, preparing a proposal, or waiting for approval. Expand the visible activity or result where more detail is available. A tool-only result can be a complete response; look for the resulting card or artifact as well as prose.

You can send a follow-up while an answer is running. It appears as queued until it starts. The queued message controls let you edit, remove, or steer work with that message. Editing returns its content to the composer; review and resend it. Steering asks the running workflow to use the selected message sooner and does not reverse actions already completed.

Use Stop to request cancellation of current chat work. A stopped response remains in the history. Inspect completed tool results before retrying: stopping generation is not a rollback, and an action that has already started may complete.

Drafts and results

Unsent text and attachment references are restored when you move between main chat, the drawer, and conversations in the same browser. Drafts are scoped to your account and organization/site/environment. They do not synchronize to another device. Sending or emptying the composer clears the draft; deleting its conversation or clearing browser site data also removes it. Signing out hides it, and signing back into the same account on that browser can restore it.

A saved draft does not send its text to an AI provider. Its uploaded files already use Ennea's file storage and retention rules. On shared devices, empty sensitive drafts or clear the site's browser data when appropriate. If browser storage is unavailable, keep the page open or copy the draft before closing it.

Use Copy on a text response. When available, use Read aloud to listen, and stop playback from the same control. Open generated file cards to preview or download results. Review calculations, sources, and assumptions before reusing them. Interactive visualizations may help explore scenarios without changing operational data.

Preferences and feedback

Personal Konnie settings offer answer length, tone, step detail, and conversation-learning participation. Select Save to retain changes or Cancel to discard them. Choose a model and its reasoning effort in the message composer. Only allowed models and supported levels appear; Ennea remembers your choice for subsequent messages and falls back to an allowed default if it becomes unavailable. Administrators manage organization models in Konnie Control Center, with optional defaults and model restrictions for groups and individual users in Administration. Organization limits always apply. A custom user policy overrides group policies; otherwise, configured groups combine by intersection. Groups with no model in common need an administrator to resolve the conflict. Dojo Mode encourages remembering useful context and remains subject to learning and memory policy. See skills and memory.

Use the response feedback controls where available and explain an incorrect result in a follow-up, including the source value that should replace it.

Recover from a problem

Symptom	Next step
Message or tool failed	Read the error and saved results; retry only the missing work.
An action needs approval	Review the target and effect, then use the approval card or ask an eligible approver.
Result seems unrelated	State the exact record, site, environment, and requested outcome again.
Very long conversation loses detail	Restate the current objective and essential constraints; use a new conversation for a separate task.
Access denied or a tool is unavailable	Ask an administrator to check your access and Konnie policy.

For groups and colleague follow-ups, see Team messages. See approvals and plans and staged changes before applying operational changes.