# Protocol of AI changes

The **AI** area of the management section contains a **Protocol** page. It lists, in
chronological order, who changed your organisation's AI settings, when that happened and
what moved. The newest change comes first.

Four events are recorded:

* **AI activated** and **AI deactivated**: switching AI features on and off for the whole
  organisation.
* **AI package switched**: moving to a different [AI package](https://lalabase.com/docs/en/guides/ai/packages) or to your own
  configuration.
* **Service tier switched**: moving between tiers within the same package.

If a package change also moves the jurisdiction in which processing happens, the entry
names both: the state before and the state after. If it additionally mentions a search
rebuild, your organisation's content was re-indexed afterwards.

<div class="docs-callout docs-callout--info">
  <div class="docs-callout__title">Why this exists</div>
  <p>The organisation itself only remembers the <strong>latest</strong> state: the current package, the current tier, the last activation. Anyone who has to show when processing abroad began or ended needs the chain, not the end state. That chain is here.</p>
</div>

<div class="docs-callout docs-callout--warning">
  <div class="docs-callout__title">What the protocol does not contain</div>
  <p>Two limits. <strong>First</strong>, the list starts when the protocol was introduced: changes made before that were never recorded and cannot be filled in afterwards, so an empty page does not necessarily mean nothing was ever changed. <strong>Second</strong>, the "own configuration" form does not write to it yet: changing the provider or the stored access key there does not appear in the protocol.</p>
</div>

The protocol is a view only. Entries cannot be edited or deleted, and the page is
restricted to administrators of the organisation.