Skip to content
roleALPHA Docs

Org Intelligence

Org Intelligence shows how your organization actually works — compared to what is formally defined. While roleALPHA maps roles, value streams, and org charts as formal structure, Org Intelligence collects anonymized interaction signals from external systems: who collaborates with whom, which value streams are actually lived, where are the informal leaders?

Prerequisite: The Org Intelligence data node (ra-signals) is switched on for your tenant.

Access Org Intelligence via the sidebar under Settings → Data & Structure → Org Intelligence (/signals). The page is only visible to Tenant Admins and Platform Admins.

Switching it on

Section titled “Switching it on”

Org Intelligence is a data node like any business module. As a tenant admin you switch it on yourself — under Settings › Data Nodes (Data Nodes). Since October 2026 there is no additional unlock: before, the “Org Intelligence” feature was needed in the subscription on top of the service, and anyone who only switched on the data node faced locked pages.

  • If the data node is on, the menu entry appears for the admins of this tenant, and all signal analyses (including the signal reports in the Aggregator) are open.
  • If it is off, the signal pages answer with “not switched on” — the tenant’s other data is unaffected.
  • A platform admin can switch the data node on on behalf of the tenant; they give a reason that appears in the log of the data nodes page.

Existing tenants that had booked the former feature were carried over during the update: where the data node had never been switched, it is now on. If the tenant admin had explicitly switched it off, that decision stands.

The servers check the switch with a delay of up to five minutes (cache per service). Right after switching on, a signal page may therefore still be locked briefly.

Troubleshooting: no data source selectable

Section titled “Troubleshooting: no data source selectable”

If the “New source” dialog lets you select no source type (empty list), the ra-signals service is not reachable for the tenant. Two prerequisites must be met:

  1. Schema present: The ra-signals tables must exist in the database. In production the fachservice deploy creates them via drizzle-kit migrate (non-destructive, no data loss). The ra-signals log must not show relation "signal_sources" does not exist.
  2. Data Node switched on: The Org Intelligence Data Node must be switched on and set up under Data Nodes. Only then is the service_registry entry for signals created. Without it the core proxy responds 503 Service 'signals' not registered and both list and dropdown stay empty.

As a platform admin, the tenant currently selected in the tenant switcher is used — data sources and signals refer to that tenant, not your home tenant. Tenant admins always operate on their own tenant only.

What is measured?

Section titled “What is measured?”

Org Intelligence evaluates metadata only — no content from messages, documents, or meetings:

SignalMeaning
Teams channel co-activityWho is a member of the same channels
Call participationWho participated in the same video calls
Calendar meetingsWho shares recurring meetings
Document co-authorshipWho edits the same documents
Comment interactionWho comments on the same pages
Jira co-assigneesWho works on the same tickets

Privacy

Section titled “Privacy”
  • Pseudonymisation: External user IDs are immediately hashed (SHA-256) on collection. Real names never leave the collector layer. This is pseudonymous, not anonymous — a hash over a known identifier is reversible if you know the input space, and the GDPR continues to apply.
  • Minimum group size: Below a minimum number of interactions or participants no metric appears — single events do not show up. The threshold has a technical floor a tenant can only raise, never lower: lowering it would revoke the pseudonymisation commitment, because a statement about a group of one person is a statement about that person.
  • 90-day TTL: All signal data is automatically deleted after 90 days.
  • Person mapping opt-in: Linking signal actors to roleALPHA persons only happens on explicit admin action. Where too little is mapped, the analysis states no ratio but the reason — a ratio over poorly mapped data would be a statement about mapping discipline rather than about the organisation.
  • Severity is relative, not absolute: How notable a value is gets measured against the percentile of observed frequencies. An absolute cut-off (“from 50 interactions”) means something entirely different in an organisation of 20 than in one of 2,000.

The values in force are in the application, not here. Under Governance Mining → Scope of analysis the platform generates a processing description with the thresholds and retention periods actually in force for your tenant — with version and date. This page explains the rule; the values there are authoritative. That way no number in the documentation can diverge from the number in the software.

What can I do with this?

Section titled “What can I do with this?”
Section titled “Related”