Reference & Data Model
Private data
Four kinds of data belong only to their creator: AI conversations, own executions, personal settings and the own timer.
Purpose
Section titled “Purpose”Besides the shared business data there are rows that are bound to a person (data type: private). Aligia enforces this binding technically, regardless of the role: even an Admin does not see other people’s conversations.
Overview
Section titled “Overview”| Data | Technical | Who sees | Who changes | Family |
|---|---|---|---|---|
| Conversation with Polaris or an agent | agent_conversation |
Creator | Creator (rename, pin, delete, send, cancel) | private |
| Workflow execution (history, graph, steps, transcript) | workflow_execution, workflow_execution_step |
Creator and Owner/Admin | Cancel: creator and Owner/Admin | private |
| Trigger fire | workflow_trigger_fire |
Same as the associated execution | – | private |
| Personal settings | user_settings |
only own | only own | account |
| Active timer | active_timer |
only own | only own | account |
| Profile picture | app_user.image_url |
all | only own | derived (special path) |
- Conversations: The creator is whoever started the conversation. If a member delegates a task or an issue to an agent, the resulting conversation belongs to the agent account; members who may read the item can read the history but not edit it. Accessing someone else’s conversation responds with “not found”, not with “forbidden”.
- Executions: What counts is the initiator of the root execution; child runs inherit the visibility. Executions without a human initiator (data-change trigger, system) are seen only by Owner/Admin.
- Own row: Personal settings and the active timer are reachable only in the person’s browser session; no workflow and no agent can read or change them.
See also
Section titled “See also”Conversation · Execution · Active timer · Personal settings · Guides › Executions