Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,075 of 9,075 pages
About the help in other languages
All help pages

Before switching on Exponential Intelligence

A checklist for administrators before editors get the Exponential Intelligence writing assistant on a live installation - decisions, provider and key, data policy, roles, review and approval, costs, the job queue…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/ai-agents/checklists/before-switching-on-exponential-intelligence.md

On this page

Before switching on Exponential Intelligence

This checklist is for administrators who are about to let editors use the assistant on a live installation. Work through it in order; each item links to the page that explains it.

Contents

  1. Decisions
  2. Provider and key
  3. Data policy
  4. Roles
  5. Review and approval
  6. Costs and the queue
  7. Records and testing
  8. The way back

Decisions

  • To do: Who will use it, for what, in which sections (An AI use policy).
  • To do: Which content must never go to an outside provider.
  • To do: Who answers questions about the processing.

Provider and key

  • To do: Provider chosen; its terms read; Region, Retention, TermsCheckedAt set (Configuring a provider).
  • To do: Key in settings/override/expai.ini.append.php only, mode 0640; not in any committed file.
  • To do: Setup > EI: Models shows "key present" and no warning about key locations.
  • To do: Test prompt of the default model answered.
  • To do: Every model that should write drafts passed the probe or is trusted (The write gate and the probe).

Data policy

Roles

  • To do: expai/write and ezjscore/call given only to the intended editors' role (Permissions for AI features).
  • To do: expai/vector, expai/chain, expai/web, expai/services given only where needed, with limitations.
  • To do: expai/summary given to the data protection officer; audit/read on channel ai to an auditor if wanted.

Review and approval

  • To do: Approval workflow on content / publish / before for the sections that need it; tested with a test editor (Drafts and human review).
  • To do: Editors know that "Send for approval" publishes at once where no approval applies.
  • To do: Editors have the review checklist.

Costs and the queue

  • To do: Monthly site budget and per-user daily limit set (Cost control).
  • To do: Cron parts expqueue (every minute) and expai (every five minutes) running, if queued work is used (Chains and queued work).

Records and testing

  • To do: The audit channel ai is written; ./console exp:audit tail --channel=ai shows a test request (The audit trail for AI).
  • To do: Signed in as a test editor: the Intelligence tab appears, a draft is written, nothing is published by itself.
  • To do: EI: Summary printed and filed with the policy.

The way back

  • To do: Everyone who may need it knows how to switch it off: [AISettings] Enabled or DisabledSiteAccesses[].

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x