# The Knowledge Base: your account's Action Statements

## Purpose
See the Action Statements and statement sets your account can build questionnaires
from, add statements of your own, and decide on the statements the AI Assistant
proposed.

## Who this is for
Account administrators and template authors working with them. Every member sees
**Knowledge Base** in the sidebar, but the page works only for members who can view
statements; of the built-in roles, **Account Manager** can view and change them. Anyone
else sees an error such as "Forbidden: requires one of statement_sets.view" above empty
sections.

## The words on this page

- **Action Statement**: one sentence describing a capability or a practice, which a
  question can be traced to. Each has facets; this page shows two of them, the **topic**
  and the **artifact**.
- **Statement set**: a named list of statements.
- **Distributed**: shared with your account by the platform. Distributed sets and
  statements are read-only here; the platform maintains them.
- **Local**: created by your account. Yours to edit and delete.

Statements from the [BIMei Ontology](/build/reference/GLOSSARY#bimei-ontology) are
offered to every account, and are listed here with the distributed ones.

## Open the page

Sidebar **Assessments** › **Knowledge Base**. The page is titled **Account Knowledge
Base**. A row of counts across the top (**Distributed sets**, **Locked sets**,
**Distributed statements**, **Labelled**, **Unlabelled**, **Local sets**, **Local
statements**, **Proposed statements**) sums up what follows. Everything is on one page,
in five sections.

## What the platform shares with you

### Distributed Sets
A table of the statement sets shared with your account: **Code**, **Title**, **Type**,
**Statements** and **Status**. Search by code, title or type, and sort by any column.
**Status** is **Locked** or **Unlocked**; a set the platform did not mark either way
counts as locked.

### Distributed Statements
Each statement is a card. The text and its facets are marked **Semantic Core
(read-only)**: "Semantic core edits are blocked in account scope." Search the text, the
topic or the artifact; filter by **Topic** and **Artifact**; and choose a **Sort by**
order.

The one thing you can change on a distributed statement is which labels your account
gives it: type label IDs under **Global Labels (IDs)** and **Local Labels (IDs)**,
separated by commas, and choose **Save Labels Only**. This works only for a statement in
a locked set shared with your account. For any other statement, including those from
the BIMei Ontology, the save is refused with "Statement not distributed to account".

## Your own statements

### Local Statements
1. Type the **Statement text**.
2. Fill in the **Topic facet** and the **Artifact facet**.
3. Optionally list **Label IDs**, **Action IDs** and **Set IDs**, separated by commas.
   **Set IDs** must be local sets of this account.
4. Choose **Create Local Statement**.

Each statement then shows its ID, its facets and how many labels, actions and sets it
has, with **Edit** and **Delete**.

### Local Statement Sets
1. Type a **Set code** and a **Set title**. Both are required.
2. Choose the **Type**: **Custom** or **Auto**. A **Filtered** set needs criteria that
   cannot be edited here.
3. List the **Statement IDs**, separated by commas. They must be distributed statements
   or local statements of this account.
4. Choose **Create Local Set**.

The **Locked** tick is recorded with the set, but it does not stop anyone editing or
deleting it.

### Deleting
Deleting a local statement or set asks you to confirm, and is permanent. There is no
check that the statement or set is in use.

## Proposed Statements

When the AI Assistant builds a template for your account, it can suggest statements
that do not exist yet. They wait here, under **Proposed Statements**, each with its
**Source blueprint:** and either the templates that use it (**Used by**) or "Not used by
any template yet."

- **Promote** keeps it as one of your local statements. From then on, the AI Assistant
  can suggest it again.
- **Reject** asks you to confirm, then withdraws it: the AI Assistant stops offering it.
  Nothing is deleted.

When every proposal has been decided, the section says "No proposed statements awaiting
review." Nothing here is sent to the platform: promoting a statement adds it to your
account only.

## Where these statements are used

- **The template builder.** Its **Action Statements** pane searches the statements your
  account can use, filtered by **All sources**, **ONT only** or **Account only**, and
  links one to a question. A question can be formally bound only to a statement from a
  locked distributed set or from the BIMei Ontology: linking a local statement records
  it as the question's source, with the note "Source recorded on the question. Template
  bindings require a locked, distributed statement set." See
  [Build an assessment template](/operate/tenant-admin/build-an-assessment-template#action-statements).
- **The BIMei AI Assistant** draws on the BIMei Ontology and on your account's own
  statements, including the proposals you promote.
- **Translations.** Your statements' text in other languages is written under
  **People & settings** › **Translations**, by choosing **Statements**; see
  [Translate statements and templates](/operate/tenant-admin/translator-workflow).

## Limits and gotchas
- **IDs, not names.** The label, action, set and statement fields take IDs, not names.
  The [Labels](/operate/tenant-admin/labels-and-label-groups) page does not display
  label IDs.
- **Proposed statements are listed twice.** A proposal also appears under **Local
  Statements**, before and after you promote or reject it.
- **Two facets of four.** A statement also has an actor and a metric, which this page
  does not show. Editing a statement here keeps them.

## Related pages
- [Build an assessment template](/operate/tenant-admin/build-an-assessment-template)
- [Labels and label groups](/operate/tenant-admin/labels-and-label-groups)
- [Translate statements and templates](/operate/tenant-admin/translator-workflow)
- [Glossary](/build/reference/GLOSSARY)
