Multi-Tenancy and Namespaces

Energyworx is a multi-tenant platform. The unit of tenancy is the namespace: an isolated environment with its own datasources, flows, rules, configurations, users and permissions. Nothing in one namespace is visible from another; every API call and console session operates within exactly one namespace.

What a namespace contains

• Data — its own datasource registry, timeseries, tags and annotations (see the Data Model).
• Processing — its own flow designs, rules, market adapters and transformation configurations.
• Users and permissions — access is granted per namespace: users are whitelisted into a namespace and receive roles through permission groups. See IAM and Permissions.
• Configuration — behaviour is tuned per namespace through Namespace Properties: market adapter assignment, IAM group mapping, processing options, and more.

A typical customer uses separate namespaces for production and acceptance/testing, so configuration can be validated before it reaches production data.

Identity and federated sign-in

Users sign in with your organisation's identity provider. The platform supports Microsoft Entra SSO and SAML federation, including automatic mapping of identity-provider groups to namespace permission groups — so joiners and leavers are handled in your IdP, not in the platform.

→ Microsoft Entra SSO · SAML · How to add a new user

Setting up a new namespace

New namespaces are provisioned and bootstrapped by administrators — see How to bootstrap a namespace.

Auditability

Actions in a namespace — user operations, flow executions, system events — are recorded as audit events, visible per datasource in the Datasources View and queryable for compliance purposes via eQL.