ClairaClaira Help Desk
Administration

How Claira uses Nuix Discover fields to store AI responses, how to create the right field types, and how to connect them in Claira settings.

Fields

Claira writes AI responses directly into Nuix Discover fields. This means every result is stored alongside your other case data, searchable, exportable, and available to everyone with access to the case. Understanding how fields work is essential to getting the most out of Claira.

The fastest way to set up fields is to let Claira create them for you, directly in Nuix Discover. See Creating fields with Claira.

What fields are used for

Every time Claira scans a document, the AI's response needs somewhere to go. That destination is a Nuix Discover field. By connecting fields to Claira, you control:

  • Where responses are saved -- which field stores the AI output
  • What gets recorded -- you can track the prompt text and a log of Claira activity in separate fields
  • Who can see results -- anyone with access to the field in Nuix Discover can see Claira's output

Most teams connect three fields:

🟒 Claira - AI ResponseMemo (one-to-many)The primary field where Claira writes the AI's answer
🟒 Claira - Prompt LogMemo (one-to-many)The Prompt Log field: records which prompt produced each response
🟒 Claira - LogMemo (one-to-many)The Log Field: records a reference for every Claira operation that touched the document

These three fields are the minimum. The prompt and log fields are typically a single field each, but for the response field we recommend setting up multiple AI response fields tailored to the tasks you plan to run. It is common to have more than one response field for a single task.

How the Log Field works

Every time a Claira operation touches a document, Claira adds a reference to that document's Log Field:

  • Bulk scan tasks write SC followed by the task number -- for example SC067 for task #067.
  • Insights write IN followed by the insight number -- for example IN012. Every document whose results fed into the insight receives the reference.

Because the Log Field is one-to-many, references accumulate: a document included in three scans and one insight carries all four references. To pull up every document a given operation touched, run a Nuix Discover search on the Log Field with the exact reference (for example, Log Field is SC067). Each task's details window and each insight's sources panel shows the exact reference to search for.

Tasks that ran before the Log Field was introduced wrote the bare task number (for example 067) instead of the prefixed form. The task details window always shows the exact value that was written for that task, so the search instructions there remain accurate for older tasks.

Setting up the Log Field and the Prompt Log field

Two of those fields have a role that Claira fills in for you, and each role is held by one connected field for the whole case:

  • Log Field: the field that collects a reference for each operation, as described above.
  • Prompt Log field: the field that records the prompt behind a value Claira wrote. Earlier versions of this page called it the Prompt Text field. Writing to it is your choice. When you save a single result to a field (Prompt Lab Apply, Multi-Code Save to fields, or saving an Agent answer), tick Also write the prompt to the Prompt Log (see Recording the prompt in the Prompt Log). For a bulk scan, tick Write the prompt to each document's Prompt Log in the confirmation dialog to record the prompt on every document the scan codes, whether the scan runs live or in the background (see Bulk scan). Neither checkbox appears unless the case has a Prompt Log field. Both start unticked in cases you were already using, a case you open for the first time starts on your latest choices from your other cases, and Claira remembers each choice for you in each case.

Let Claira set them up

While either role has no field, the Connected fields section in Settings shows a Set up your log fields box (or Set up a Log Field, or Set up a Prompt Log field, when only one is missing). The box lists what Claira will do, and one click does it:

  1. Click Create and connect.
  2. For each missing role, Claira first looks for a connected Memo field that already carries the role's name, such as 🟒 Claira - Log and 🟒 Claira - Prompt Log, the Claira Log and Claira Prompt Log names Claira created before, or the Log Field and Prompt Text names this page used to recommend, in any of Claira's languages. If that field has no role yet, Claira gives it the role instead of creating a duplicate.
  3. If no connected field fits, Claira looks at the fields this case used before and has since disconnected. A Memo field with one of those names is connected again with the role (the box says reconnect), and it keeps its history in Claira. While Claira checks, the box says so and the button waits. Discover does not let Claira look a field up by name, so a field that was never connected to Claira cannot be found this way.
  4. Otherwise Claira creates a Memo field in Nuix Discover, named 🟒 Claira - Log or 🟒 Claira - Prompt Log in your language, and connects it with its role. Every field name Claira proposes starts with 🟒 Claira -, so Claira's fields sit together in the Nuix Discover field list and are easy to recognize as AI fields. If a field on the case, connected or disconnected, already uses that name, Claira adds a number, for example 🟒 Claira - Log 2.
  5. Claira sets up the fields one at a time, and the box lists what happened to each. When nothing needs creating, the button reads Use these fields.

Discover creates new fields with no group access. When Claira has created a field, the box says so and offers Copy instructions for your admin: send the copied message to a case administrator. It names each new field and the two steps that grant read and write access. Until then, scans cannot write to the new fields.

If something could not be done, the box says why and what to do next:

  • Your Discover role does not allow creating fields. Claira stops rather than trying the next field. Ask a case administrator to create the missing Memo fields, then connect them with Connect new field.
  • Your role in your organization does not allow setting the log fields. This applies whether Claira was connecting, reconnecting or creating a field. Claira stops rather than trying the next field, lists the fields it did not try, and does not offer Try again, because a new attempt would be refused the same way. Connecting the field yourself would be refused for the same reason, so ask your organization's Claira administrator to set up the log fields, or to change your role.
  • The portal cannot create fields from Claira. Create the missing Memo fields in Discover, then connect them with Connect new field.
  • Discover already has a field with that name that has never been connected to Claira. Discover does not tell Claira which field it is, so click Connect new field: the form opens with the field's name and its role already filled in, and you only add its composite ID.
  • Anything else. Click Try again.

Click Done to close the box.

Assign a role yourself

To give a connected field a role, click its pencil button in Connected fields and tick Intended for Log Field or Intended for Prompt Log. A role has one field at a time, so ticking the box on one field removes the role from any other. The change is recorded in the case's audit trail, and if your organization's role does not allow it, Claira says so and nothing changes.

Giving a field a logging role in a conversation

In Agent Mode, you can ask Claira to give a connected field one of the two logging roles, for example "Make 🟒 Claira - Log our Log Field." Claira answers with a Set a logging role card:

  • The card names the field and the role it would hold, and says which field holds that role now, or that no field holds it yet. If the field already holds the role, the card says that nothing will change.
  • Nothing changes until you select Set role on the card. Agreeing in the conversation is not enough, and Cancel ends the offer. To use a different field, ask Claira in the conversation: the card shows only the field it proposes.
  • After Set role, the card names the field that now holds the role, and Connected fields in Settings shows the role's badge on it.

When a role moves:

  • One field holds each role for the whole case, so the change applies to everyone working in the case, from their next scan. The field that held the role before stops receiving new entries.
  • Nothing already written to either field changes, and a bulk scan that is already running keeps writing to the Log Field it started with.

Claira checks the field when it shows the card, and again when you select Set role:

  • The field must be connected to the case, and Claira must be able to write to it. A field still waiting on admin access cannot hold a role yet.
  • It must be a Memo field. If you do not have one, ask Claira to create it (see Creating fields in a conversation). In Settings you can still give a role to a field of another type.
  • One field cannot hold both roles.
  • If someone else moves the role while the card is open, the card updates to name the new holder and asks you to review it before you select Set role again.

Every role change, whether made in Settings, by the one-click setup or on a card, is recorded in the case's audit trail with who made it. If your organization has switched on role enforcement and your role does not include Designate the prompt or task log field, Claira says so and the role stays where it was.

Claira cannot connect an existing Discover field for you from a conversation. To use a field that is not connected yet, connect it first with Connect new field in Settings (see Connecting an existing field).

Tailoring response fields to your tasks

Different review tasks produce different kinds of output, and routing each kind into its own field keeps results easy to search, sort, and export. Below are two common workflows and the response fields they typically use.

Metadata enhancement (objective coding)

When Claira is filling in or correcting document metadata, each metadata point usually lives in its own field:

DateMemo (one-to-many)Document date extracted by Claira
TitleMemo (one-to-many)Document title or subject
AuthorMemo (one-to-many)Author or sender
RecipientMemo (one-to-many)Recipient(s)
KindMemo (one-to-many)Document kind (email, contract, memo, etc.)

Relevance review

Relevance tasks often pair a decision with the supporting context that justifies it:

Relevance decisionMemo (one-to-many)Responsive / not responsive
Relevance justificationMemo (one-to-many)Why Claira reached this decision
Issue tagMemo (one-to-many)Which case issue the document touches
Relevance confidence scoreMemo (one-to-many)How confident Claira is in the decision

These are just examples -- tailor your response fields to the specific tasks your reviewers will run.

If you are configuring Claira in a case you plan to clone for future matters (sometimes called the clone case), set up a broad range of AI fields up front. A comprehensive field library on the clone case means any future task can be performed without revisiting field setup.

Two ways to add a field

There are two ways to make a field available to Claira:

  • Create it with Claira (recommended). Claira creates the field in Nuix Discover and connects it automatically, with no composite ID to look up. From Connected fields in Settings, or from any field picker, open the Create in Discover tab. The full walkthrough (including the administrator access step that follows creation) is in Creating fields with Claira.
  • Connect an existing field. If the field already exists in Nuix Discover, if you need a pick list field (Claira cannot create those), or if your portal doesn't support creating fields from Claira, connect the field by its Composite ID as described below.

Connecting an existing field

Creating the field in Nuix Discover

Claira works best with memo fields with one-to-many cardinality. This field type allows multiple values per document, which is important because you may run several prompts against the same document over time.

To create a new field:

  1. Navigate to field management in your Nuix Discover case.
  2. Create a new field with the following settings:
    • Type: Memo
    • Cardinality: One-to-many
    • Name: Something descriptive that includes the field's purpose
We recommend including the Composite ID in the field name. This makes it much easier to connect the field in Claira later, especially when you have many fields in a case.

Finding the Composite ID

Every Nuix Discover field has a Composite ID -- a unique identifier that Claira uses to connect to the right field. You need this ID when connecting an existing field in Claira settings.

To find the Composite ID:

  1. Open your browser's developer tools (press F12 or right-click the page and select Inspect).
  2. Switch to the Network tab.
  3. Navigate to the field in Nuix Discover (for example, open the field in the coding panel or field management).
  4. Look for the API request that loads field data. The Composite ID appears in the response.

The Composite ID looks something like this:

🟒 Claira - AI ResponseMemo (one-to-many)CASE.PREP.CLR_RESP

Connecting the field in Claira

Once you have your fields created and their Composite IDs noted, connect them in Claira:

  1. Open the Claira pane in your workspace.
  2. In Settings, open Connected fields and click Connect new field.
  3. On the Connect existing tab, paste the Composite ID.
  4. Give the field a label that your team will recognize.
  5. Optionally, add notes to explain what the field is used for.
Privilege FlagMemo (one-to-many)CASE.PREP.CLR_PRIVStores privilege determination from AI review

Each connected field is a row in Connected fields: its label, then its composite ID and who connected it, with a Prompt Log Field or Log Field badge when it holds that role. Long names are shortened to fit the pane; hover a name to read it in full. The pencil button at the end of the row edits the field, and the broken-link button disconnects it.

Shared visibility

When you connect a field in Claira, that connection is shared across all users on the case. This means:

  • You only need to connect fields once per case.
  • Every user who opens Claira will see the same field connections.
  • Any user can write to the connected fields by running scans.
  • The Log Field and the Prompt Log field are case-wide too: each role is held by one field for everyone on the case.
Because fields are shared, coordinate with your team before changing field connections on an active case. Changing a connected field mid-review could route new results to a different location than earlier results.

Disconnecting fields

You can disconnect a field from Claira at any time from Connected fields in Settings, using the broken-link button at the end of the field's row. Claira asks you to confirm, and says what disconnecting does, before anything changes.

  • If a bulk scan is currently running or queued and writes to the field, the disconnect is blocked. Wait for the scan to finish, or cancel it, then disconnect the field.
  • If teammates have the field selected in their scan settings, you can still disconnect it. Their selection is cleared automatically, and they simply pick a different field the next time they run a scan.

Disconnecting a field only removes the connection between Claira and the field. The field itself -- and every AI response already written to it -- stays untouched in Nuix Discover, and past scan results and history in Claira are unaffected.

If you reconnect the same field later (same Composite ID), it picks up right where it left off.


Need help? Contact us at support@claira.to.

Was this page helpful?

Need more help?

Contact our support team at support@claira.to β€” we are here to help.

On this page