Configure Assistant Operations
Set team automation defaults, give Assistant business context, create proactive controls, and keep consequential actions supervised.
This guide configures the operational layers around Assistant. Start with team-wide automation defaults, then add business context, goals, watchers, and scheduled work. Enable Autopilot only after the approvals process is working.
Prerequisites
- You can sign in to an Eigenn team workspace.
- The required bank, accounting, invoice, payment, or communication apps are connected and current.
- Your team has chosen an approvals owner.
- You know which outward actions, if any, may run without asking first.
1. Record Team Automation Preferences
Open Settings → Automation.
Webhook Configuration
- Choose Retry Attempts: No retries, 3 retries, or 5 retries.
- Choose Timeout: 10 seconds, 30 seconds, or 60 seconds.
- Choose Save in this section.
Three retries and a 30-second timeout are the saved defaults.
Data Sync
- Turn Enable Auto Sync on or off.
- Choose Sync Frequency, from Every 3 hours through Every 24 hours in three-hour steps.
- Choose Save in this section.
Automatic sync every three hours is the saved default.
Workflow Limits
- Set Max Concurrent Workflows to 2 workflows, 4 workflows, or 6 workflows.
- Set Workflow Timeout to 15 minutes, 30 minutes, or 60 minutes.
- Choose Save in this section.
Two concurrent workflows and a 30-minute timeout are the saved defaults.
Slack Notifications
- Paste a valid incoming URL into Slack Webhook URL.
- Turn on Enable Slack Notifications.
- Choose Save in this section.
This is the team-wide automation notification setting. It does not make the Slack choice on an individual watcher deliver watcher crossings; current watcher crossings appear in Workspace → Approvals.
These settings currently record team preferences; they do not yet change webhook delivery, integration sync, workflow execution, or Slack notification behavior. Check the owning feature for actual behavior. A successful Save confirms storage, not enforcement or delivery.
2. Add Business Context
Open What I know about your business in the Assistant operation pages.
- Enter Industry.
- Choose the month under Fiscal year starts.
- Enter Base currency.
- Describe Primary goals and Focus areas.
- Add durable context under Notes.
- Choose Save and wait for Business profile saved.
Use facts that are stable across many conversations. Keep one-off scenario assumptions in the prompt or forecast instead of the business profile.
3. Create the First Goal
Open Goals.
- Choose New goal.
- Enter a label such as “Keep runway above 6 months.”
- Enter the metric name, for example
runway. - Choose the direction and target.
- Add a due date when the goal has a deadline.
- Choose Create goal.
Use the status selector to mark the goal Active, Met, Missed, or Archived as it resolves. The visible progress bar currently reflects status, not a continuously calculated metric percentage.
4. Create a Supported Watcher
Open Watchers.
- Choose New watcher.
- Describe the business meaning of the alert.
- Enter a supported metric such as
runway,runway_projected,cash_projected,breach_probability,overdue_ar,promises_at_risk, ordso. - Choose is below, is at or below, is above, is at or above, or equals.
- Enter a numeric threshold.
- Choose Daily, Weekly, or Monthly.
- Keep In-app as the operational channel for current delivery.
- Choose Create watcher.
Use Pause when the rule is temporarily irrelevant and Delete when the rule should no longer exist.
You can also create a daily Runway watcher from the eye icon on Overview. That control pre-fills the current value and only appears for supported metrics.
5. Create a Scheduled Prompt Carefully
Open Scheduled runs.
- Choose New scheduled run.
- Give the run a clear name.
- Write a self-contained prompt with its time range and desired output.
- Leave Agent (optional) blank unless you know the supported agent identifier.
- Choose Hourly, Daily, Weekly, or Monthly.
- Choose the requested delivery channel.
- Choose Create scheduled run.
Use Pause, Enable, and Delete to control the saved run.
Current scheduled prompts record a queued request for the period. They do not yet produce a completed background Assistant response, and Slack or email result delivery is not available from this path. Use the row's last status and Workspace → Approvals to distinguish a recorded request from completed work.
6. Establish the Human Approval Loop
Open Workspace → Approvals before turning on Autopilot.
- Filter to Open.
- Select a proposal and review its plain-language action, amount, source context, and cash impact.
- Choose Claim to take ownership.
- Choose Approve or Reject.
- Confirm that approved work reaches Done or Failed.
- Test Undo on a reversible, non-production example while its undo window is open.
Assign a person to check Approved items that have not advanced. Approval records intent; a separate process executes the action.
7. Review Action Bundles
Open Action Bundles when a projected cash-floor watcher creates grouped work.
- Read the total cash impact and runway preview.
- Review every line independently.
- Use Approve all only when every line is acceptable.
- Otherwise use Approve or Drop on individual lines.
- Return to Workspace → Approvals to follow execution status.
The runway preview can be absent when burn history is insufficient or the business is net positive. Never infer a zero impact from a missing preview.
8. Configure Autopilot Last
Open Autopilot.
- Leave Enable autopilot off while drafting the policy.
- Enter exact, comma-separated action identifiers under Allowed actions (comma-separated action ids).
- Set Max amount. Keep a cap unless there is a reviewed reason not to.
- Set a positive whole-number Undo window (minutes).
- Turn on Enable autopilot.
- Choose Save.
Start with one reversible action. Autopilot only considers an action when the policy is enabled, the identifier exactly matches, the estimated amount is known and within the cap, and the action is not irreversible.
An empty Max amount means no monetary cap. It does not weaken the exact allow-list or the irreversible-action block.
9. Verify the Audit Trail
Open Autopilot audit after the first autonomous action.
Confirm that the entry includes:
- a clear summary,
- the action identifier,
- the reason,
- any failure state, and
- whether the undo deadline remains open.
Use Workspace → Approvals for the actual Undo control. The audit page is read-only.
10. Run a Controlled Acceptance Check
Before considering configuration complete:
- Ask Assistant a read-only question using connected data.
- Create one supported watcher with a threshold you can safely observe.
- Confirm a crossing appears in Workspace → Approvals at most once for its period.
- Approve or reject a harmless proposal.
- Confirm the status reaches a terminal state.
- If Autopilot is enabled, verify one allow-listed reversible action and its audit entry.
- Check that an unlisted or over-cap action still waits for human review.
What Success Looks Like
Assistant operations are configured when:
- all four Settings → Automation sections reflect intentional team preferences and the team understands that they are not yet enforcement controls,
- stable business context is saved,
- goals and watchers use recognized metrics,
- the approvals queue has a named operator,
- scheduled prompts are understood as queued requests rather than completed work,
- Autopilot is narrow, capped, reversible, and tested, and
- the team verifies terminal status and audit evidence rather than assuming completion.
Troubleshooting
A section in Settings did not retain my changes
Each section saves independently. Return to that section, review the values, and choose its own Save button.
Auto Sync is on but Assistant data is stale
The saved preference does not yet enforce integration sync timing. Confirm the integration is connected in Marketplace, run the owning feature's supported refresh or sync workflow, and inspect the detailed product page.
A metric name saves but never evaluates
The Watchers form accepts text, but proactive checks can evaluate only supported metrics. Replace the name with a canonical metric listed in this guide.
A watcher selected Slack or Email but only appears in Approvals
That is the current behavior. Slack and email watcher delivery is not available yet.
A scheduled run has no completed answer
Scheduled prompt runs currently record queued requests. Review Workspace → Approvals and do not treat the saved schedule or queued status as delivered output.
Autopilot stays inactive after saving
Confirm Enable autopilot is on, at least one exact action identifier is present, the amount is within the cap, and the action is reversible. Ask support to confirm proactive processing is enabled for the workspace.
Undo is missing
Undo appears only for Done or Executing actions with an unexpired undo deadline. An action without a window, an expired action, or a non-executed proposal cannot be undone.
An approval is stuck
Check Approved, Executing, and Failed. Because execution is separate from approval, contact support when an approved item does not advance and proactive processing should be active.