Skip to content

Assistant Settings

The AI Assistant settings page is the control center for Eric usage and billing. Durable Eric guidance now lives in the Company Knowledge workspace.

  • Admins and Giga Admins can open the full settings page, including Billing & Credits
  • Any user with Eric access can open a read-only Usage view from the chat sidebar

Non-admin users can use chat if permitted, but they cannot manage billing or capacity.

The Usage tab shows how active your team is and gives a compact current-period credit summary. Admins see the full tab here; non-admins can view a read-only version from the chat sidebar.

A ring chart shows Weekly AI Credit Allowance used in the current period. Next to it you will see:

  • Total available - usable Weekly AI Credit Allowance plus One-Off AI Credits
  • Weekly remaining - the remaining weekly allowance and the next reset time
  • Manage credits - a shortcut to the Billing & Credits tab for admins

The Weekly AI Credit Allowance resets weekly. Unused weekly allowance does not roll over and does not become One-Off AI Credits.

Cards display:

  • Team activity over the last year
  • Day streak
  • Next sessions milestone
  • Positive feedback rate
  • Total sessions and sessions in the last 7 days
  • Active users and sessions in the last 30 days
  • Messages sent and total runs
  • Total tool calls across all sessions

When your team has activity, a leaderboard ranks users by credits consumed, with columns for sessions, messages, and last active date.

The Billing & Credits tab is the full AI capacity and billing workspace. It shows AI Credit Availability split into the parts that can be used by Main Eric Chat:

  • Weekly AI Credit Allowance - recurring weekly capacity from the subscription tier and any active AI Add-On
  • One-Off AI Credits - manually purchased overflow credits available after the weekly allowance is exhausted
  • Total usable AI Credits - a secondary summary of available weekly and one-off capacity

One-Off AI Credits roll over across weekly periods until their AI Credit Expiration, one year after purchase. When multiple One-Off Credit Batches are available, Eric consumes the earliest-expiring credits first.

The Billing & Credits tab lists individual One-Off Credit Batches so admins can audit purchased overflow capacity. Each batch shows:

  • Remaining AI Credits
  • Purchased AI Credits
  • AI Credit Expiration
  • State: usable, Reserved One-Off AI Credits, or expired

Reserved One-Off AI Credits are credits held while the Company is not currently a Paid Company. They can become usable again if paid status returns before their original AI Credit Expiration.

Admins see a Credit Expiration Warning on the Billing & Credits tab when One-Off AI Credits are within 30 days of AI Credit Expiration.

Paid Company admins can use AI Capacity Management on the Billing & Credits tab to:

  • Buy One-Off AI Credits in 1,000-credit increments
  • Manage an AI Add-On that increases Weekly AI Credit Allowance in 1,000-credit increments

AI Add-Ons are added weekly capacity billed monthly. Confirmed increases apply immediately; decreases and cancellations take effect at the next monthly renewal.

Admins can review AI Credit Purchase History on the Billing & Credits tab for one-off purchases, AI Add-On increases, AI Add-On decreases, cancellations, and outcomes. Purchase history tracks:

  • Who started the change
  • Where it started
  • When it was confirmed
  • The quantity involved
  • The outcome: confirmed, pending, failed, or cancelled

If a Company runs out of usable AI Credits while an already-admitted Eric Run is still in progress, the run completes normally. The overrun is recorded as an audit detail in the Billing & Credits tab for transparency. It does not create credit debt, reduce a future Weekly AI Credit Allowance, or consume future One-Off AI Credits.

If a Company has no usable Weekly AI Credit Allowance or One-Off AI Credits, Eric blocks new Main Eric Chat runs until more usable AI Credits are available. Non-admin Users see a concise message asking them to contact an admin. Admins see actions to buy One-Off AI Credits or manage the AI Add-On.

The Company Knowledge workspace presents the durable areas of the Eric Filesystem as one permission-filtered space. Map provides a visual overview, while Files provides a literal folder hierarchy for accessible Markdown Knowledge Files, YAML Definition Files, and generated system files. Session-scoped Scratch content stays in its Eric conversation and does not appear here.

Key areas include:

  • The signed-in user’s Personal Knowledge Directory for private notes and preferences
  • Company, Dataset, and Query Dataset knowledge the user can access
  • Knowledge Proposals for Eric-created company-wide updates that need approval
  • Dashboard, Query Widget, and Query Dataset Definition Files that can be inspected as read-only YAML and opened in their owning product workspace

Eric starts each run with a compact Knowledge Filesystem bootstrap, then reads and updates visible Knowledge Files with virtual terminal-style tools while working.

  • Put evergreen business logic into Company Knowledge, not one-off chat prompts
  • Keep user-specific preferences in the Personal Knowledge Directory
  • Use Dataset knowledge for rules that should follow a Dataset or Query Dataset
  • Review Company Knowledge Proposals before approving shared changes