Reference & Data Model
Technical accounts and principals
Besides people, three kinds of technical accounts act in Aligia: the System account, the Polaris account and the accounts of activated agents.
Purpose
Section titled “Purpose”Every write action needs an author. If it is not a person but the system, Polaris or an agent that acts, the row carries a technical account (data type: identity). All technical accounts are user accounts with a kind other than human; in the activity history their actions appear with a label („Agent“, „System“, „Automatisch“ (Automatic)).
The accounts
Section titled “The accounts”| Account | Kind (kind) |
Display name | Active | When it is created | What for |
|---|---|---|---|---|---|
| System account | tenant_system_user |
„System“ | no | On provisioning of the organization, at the latest on first login | Author for writes without a human or agent trigger: trigger fires on data changes, synchronization of MCP tools |
| Polaris account | polaris |
„Polaris AI“ | yes | On a member’s first login | Delegation target: tasks and issues can be delegated to „Polaris AI“; mention in comments |
| Agent account | agent |
Name of the agent | follows the agent’s status | On activating an agent (Owner/Admin only) | Delegation target and author of this agent’s actions |
Exactly one System and one Polaris account per organization; at most one account per agent (1:1). When an agent is deactivated its account becomes inactive, on re-activation it becomes active again and the display name is updated from the agent’s name. For activation the agent’s name and model must be valid.
Principal kinds
Section titled “Principal kinds”For every action Aligia distinguishes who is responsible (principal) and who executes (executor):
Responsible (responsible) |
Meaning | Permissions |
|---|---|---|
Person (human) |
A signed-in member | The member’s role |
Agent (agent) |
An activated agent | As described below |
Organization service account (tenant_system_user) |
Aligia itself on behalf of the organization (delegation, workflow triggers, synchronization) | Own access on the whole organization and every unit, never Admin |
Platform service (platform) |
Operator processes (provisioning) | Operator endpoints only |
Executors are human, polaris, agent, tenant_workflow, platform_workflow or file_server.
Who may do what
Section titled “Who may do what”| Actor | Acts as | Data access |
|---|---|---|
| Polaris in a member’s chat | The person (the person’s session) | Exactly the person’s permissions: read/write all business data, admin tables only with the Admin role. Polaris can never do more than you |
| Own agent in the chat | The person, but with a limited tool set | Only read access to Aligia data (lookups, queries), plus one-off workflows and – if connected – MCP tools. No write tools |
| Delegated agent (task/issue delegated to an agent or „Polaris AI“) | Organization service account, writes as the agent account | Read and edit business data with the service account’s access; configure nothing (no Admin) |
| Workflow via trigger (data change) | Organization service account, author „System“ | Only the actions released for the workflow family |
| System (cascades, derivations, KPI calculation, optimizer commit) | Service | Writes derived data; in the activity history as „System“, „Kaskade“ (Cascade), „Optimierung übernommen/zurückgesetzt“ (Optimization applied/reset) |
See also
Section titled “See also”Agent · Conversation · Trigger · User account · Guides › Agents · Guides › Polaris