Chat — Workflow

Overview

The Chat module follows the standard catalog lifecycle in SARA. Both assistants and threads are created in an active state and can be deactivated or reactivated as needed. There is no approval pipeline.

No approval pipeline

This feature does not have a multi-step approval workflow. Records are managed directly with no intermediate statuses between active and inactive.

Note

For the standard catalog lifecycle pattern, see: Workflows & Pipelines

Status lifecycle

Both assistants_gtp and threads_gtp records use the same two statuses:

ACTV — Active. The record is available. Active threads appear in the main chat view; active assistants appear as tabs.
INAC — Inactive. The record is deactivated. Inactive threads and threads belonging to inactive assistants are hidden from the main chat view.

Info

For system-wide status guidance, see: Status

Lifecycle notes

Thread visibility: only threads with status ACTV and belonging to an ACTV assistant are shown in the main chat view. A thread may be active in the database but invisible if its parent assistant is inactive.

Cascading deactivation: deactivating an assistant automatically sets all of its threads to INAC. This is irreversible from the assistant action — each thread must be reactivated individually from the All Chats tab in the AI set up modal.

Reactivation: reactivating an assistant does not restore its threads. Threads must be reactivated separately by an admin with edit permission.

New thread creation: when a user creates a new thread, SARA calls OpenAI to create a thread object and stores the returned thread string ID. The thread is created with status ACTV and immediately available in the chat view.

Assistant registration: when an admin registers a new assistant, SARA validates the provided OpenAI string ID against the OpenAI API before saving. If the string is invalid or the assistant does not exist on OpenAI, the registration is rejected.

Permissions

Access and actions are permission-driven. See: Permissions