Centurio System- & Moduldokumentation
🔍
🏛️ Plattform-Architektur
🇩🇪 Deutsch 🇬🇧 English 🇫🇷 Français 🇪🇸 Español 🇮🇹 Italiano 🇳🇱 Nederlands 🇵🇱 Polski 🇵🇹 Português 🇨🇿 Čeština 🇸🇰 Slovenčina 🇭🇺 Magyar 🇷🇴 Română 🇧🇬 Български 🇬🇷 Ελληνικά 🇩🇰 Dansk 🇫🇮 Suomi 🇸🇪 Svenska 🇱🇹 Lietuvių 🇱🇻 Latviešu 🇪🇪 Eesti 🇭🇷 Hrvatski 🇸🇮 Slovenščina 🇲🇹 Malti 🇮🇪 Gaeilge 🇷🇺 Русский 🇺🇦 Українська 🇹🇷 Türkçe 🇳🇴 Norsk bokmål 🇷🇸 Српски 🇮🇸 Íslenska 🇨🇭 Schwiiz/Suisse
🔑 Login
🏠 Alle Module / crm_office / Kommunikation & Postfächer
📘

Kommunikation & Postfächer

communications crm_office 🛡️ RLS Protected

Kommunikation & Postfächer — aus Code abgeleitete Prozess- und API-Dokumentation.

Fachliche Bestimmung: Kommunikation & Postfächer — aus Code abgeleitete Prozess- und API-Dokumentation. Erfasst alle registrierten Prozesse, Capabilities, Zustandsmaschinen, APIs und Tabellen für Simulationen und Reviews.
⚡ Workflows & Lebenszyklen (1) 🗄️ Datenmodelle & Felder (6) 🔌 Einstiegspunkte (UI & APIs) (30) 🛡️ Regulatorik & Compliance

⚡ Workflows & Lebenszyklen

Benutzerbefehl: reply agent plan:command_reply_agent

Geprüfter Durable-Plan (durable_plan), Start: manual_command.

1. reply_agent
reply_agent
{"key": "execute_command", "label": "Befehl prüfen, ausführen oder zur Freigabe vorlegen", "adapter": "agent.execute", "agent": "reply_agent", "condition_fact": null}
Aktionen: reply_agent

🗄️ Datenmodelle & Felder

Communications communications RLS Aktiv
20 Felder / Spalten

Tabelle communications

Feldname Datentyp Pflicht Schlüssel Fachliche Bedeutung
channel VARCHAR(32) Ja * - Feld channel
direction VARCHAR(16) Ja * - Feld direction
sender VARCHAR(320) Nein - Feld sender
recipients ARRAY Ja * - Feld recipients
subject VARCHAR(512) Nein - Feld subject
body_text TEXT Nein - Feld body_text
body_html TEXT Nein - Feld body_html
sent_at DATETIME Nein - Feld sent_at
customer_id UUID Nein FK ➔ customers.id Feld customer_id
project_id UUID Nein FK ➔ projects.id Feld project_id
external_message_id VARCHAR(512) Nein - Feld external_message_id
id UUID Nein PK Feld id
tenant_id UUID Ja * FK ➔ organizations.id Feld tenant_id
created_at DATETIME Ja * - Feld created_at
updated_at DATETIME Ja * - Feld updated_at
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata
NetworkCapabilities network_capabilities RLS Aktiv
10 Felder / Spalten

Tabelle network_capabilities

Feldname Datentyp Pflicht Schlüssel Fachliche Bedeutung
profile_id UUID Ja * FK ➔ network_profiles.id Feld profile_id
name VARCHAR(128) Ja * - Feld name
level VARCHAR(32) Nein - Feld level
certified BOOLEAN Ja * - Feld certified
notes TEXT Nein - Feld notes
id UUID Nein PK Feld id
tenant_id UUID Ja * FK ➔ organizations.id Feld tenant_id
created_at DATETIME Ja * - Feld created_at
updated_at DATETIME Ja * - Feld updated_at
metadata JSONB Ja * - Feld metadata
NetworkMatches network_matches RLS Aktiv
15 Felder / Spalten

Tabelle network_matches

Feldname Datentyp Pflicht Schlüssel Fachliche Bedeutung
demand_id UUID Ja * - Feld demand_id
candidate_type VARCHAR(32) Ja * - Feld candidate_type
candidate_id UUID Ja * - Feld candidate_id
candidate_name VARCHAR(255) Ja * - Feld candidate_name
score NUMERIC(5, 4) Ja * - Feld score
status VARCHAR(48) Ja * - Feld status
id UUID Nein PK Feld id
tenant_id UUID Ja * FK ➔ organizations.id Feld tenant_id
created_at DATETIME Ja * - Feld created_at
updated_at DATETIME Ja * - Feld updated_at
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata
NetworkOfferings network_offerings RLS Aktiv
14 Felder / Spalten

Tabelle network_offerings

Feldname Datentyp Pflicht Schlüssel Fachliche Bedeutung
profile_id UUID Ja * FK ➔ network_profiles.id Feld profile_id
title VARCHAR(255) Ja * - Feld title
description TEXT Nein - Feld description
product_id UUID Nein - Feld product_id
price NUMERIC(14, 2) Nein - Feld price
currency VARCHAR(3) Ja * - Feld currency
availability VARCHAR(32) Nein - Feld availability
lead_time_days INTEGER Nein - Feld lead_time_days
active BOOLEAN Ja * - Feld active
id UUID Nein PK Feld id
tenant_id UUID Ja * FK ➔ organizations.id Feld tenant_id
created_at DATETIME Ja * - Feld created_at
updated_at DATETIME Ja * - Feld updated_at
metadata JSONB Ja * - Feld metadata
NetworkProfiles network_profiles RLS Aktiv
18 Felder / Spalten

Tabelle network_profiles

Feldname Datentyp Pflicht Schlüssel Fachliche Bedeutung
profile_type VARCHAR(48) Ja * - Feld profile_type
linked_entity_type VARCHAR(32) Nein - Feld linked_entity_type
linked_entity_id UUID Nein - Feld linked_entity_id
display_name VARCHAR(255) Ja * - Feld display_name
description TEXT Nein - Feld description
vat_id VARCHAR(32) Nein - Feld vat_id
address_text TEXT Nein - Feld address_text
visibility VARCHAR(16) Ja * - Feld visibility
active BOOLEAN Ja * - Feld active
id UUID Nein PK Feld id
tenant_id UUID Ja * FK ➔ organizations.id Feld tenant_id
created_at DATETIME Ja * - Feld created_at
updated_at DATETIME Ja * - Feld updated_at
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata
Notifications notifications RLS Aktiv
19 Felder / Spalten

Tabelle notifications

Feldname Datentyp Pflicht Schlüssel Fachliche Bedeutung
user_id UUID Ja * FK ➔ users.id Feld user_id
kind VARCHAR(32) Ja * - Feld kind
title VARCHAR(255) Ja * - Feld title
body TEXT Nein - Feld body
link VARCHAR(512) Nein - Feld link
entity_type VARCHAR(64) Nein - Feld entity_type
entity_id UUID Nein - Feld entity_id
actor_user_id UUID Nein FK ➔ users.id Feld actor_user_id
dedupe_key VARCHAR(160) Nein - Feld dedupe_key
read_at DATETIME Nein - Feld read_at
id UUID Nein PK Feld id
tenant_id UUID Ja * FK ➔ organizations.id Feld tenant_id
created_at DATETIME Ja * - Feld created_at
updated_at DATETIME Ja * - Feld updated_at
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata

🔌 Einstiegspunkte (UI & APIs)

Art Methode Endpunkt / Pfad Titel & Zweck Berechtigung
⚡ REST API DELETE /api/v1/communications/mailboxes/{account_id}
delete_mailbox
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API GET /api/v1/communications
list_communications
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/communications/mailboxes
list_mailboxes
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/communications/mailboxes/presets
get_mailbox_presets
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/communications/mailboxes/{account_id}
get_mailbox
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/communications/{comm_id}
get_communication
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/meetings/{room_key}
meeting_info
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/network/demands
list_demands
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/network/profiles
list_profiles
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/notifications
list_notifications
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /api/v1/notifications/count
unread_count
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API GET /communications
communications_page
Semantic binding: not_evaluated; mutation=False
 communications
⚡ REST API PATCH /api/v1/network/demands/{demand_id}/status
update_demand_status
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/communications/mailboxes
create_mailbox
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/communications/mailboxes/autodiscover
autodiscover_mailbox
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/communications/mailboxes/test-draft
test_draft_mailbox
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/communications/mailboxes/{account_id}/sync
sync_mailbox_now
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/communications/mailboxes/{account_id}/test
test_mailbox_connection
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/communications/{comm_id}/forward-to-inbox
forward_communication_to_inbox
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/meetings
create_meeting
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/meetings/{room_key}/end
end_meeting
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/meetings/{room_key}/invite
invite
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/network/capabilities
create_capability
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/network/demands
create_demand
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/network/demands/{demand_id}/convert
convert_lead
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/network/demands/{demand_id}/match
match_demand
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/network/demands/{demand_id}/propose
create_proposal
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/network/profiles
create_profile
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API POST /api/v1/notifications/read
mark_read
Semantic binding: not_evaluated; mutation=True
 communications
⚡ REST API PUT /api/v1/communications/mailboxes/{account_id}
update_mailbox
Semantic binding: not_evaluated; mutation=True
 communications

🛡️ Regulatorik & Compliance

Dieses Modul unterliegt folgenden gesetzlichen, regulatorischen und Revisionsstandards:

  • GoBD Nachvollziehbarkeit
  • Mandanten-Isolation (PostgreSQL RLS)