Platform architecture

Every tenant's data is isolated at the API layer — no request can read or write across a workspace boundary. A Platform Admin layer sits above individual tenants: it onboards new tenants, assigns each one to an Industry, and defines the base ontology every tenant in that industry inherits.

Inside a workspace, four roles apply: Tenant Admin and Analyst can configure data sources, entities, and ontology versions; Viewers can see dashboards and export data but can't change configuration; Platform Admins retain oversight across every tenant. Every state-changing request is checked against the caller's role before it runs.

Each Industry has a base ontology — the topic/keyword taxonomy analytics run against by default. A tenant can override it, and every override save creates a new version rather than replacing the last one, so any prior version (or the platform default) can be reactivated instantly if a change doesn't work out.

Tenants choose per data source whether to route collection through SocialPulse's managed aggregator connections, or connect their own API credentials directly. Both paths converge on the same enrichment pipeline and the same post schema, so analytics behave identically regardless of source.