How LUMA connects to workspaces and portals

A workspace connects the CMP Angular application to a LUMA instance, which provides authentication and user management. Behind the scenes, the workspace holds a link to its associated LUMA deployment and a service account token that authorises CMP to communicate with LUMA.

A single CMP deployment can contain multiple workspaces, each pointing to its own LUMA instance or sharing one, depending on the implementation.

LUMA provides two things that Storyteq CMP depends on: authentication and services.

Authentication controls who can log in to a workspace. When a workspace is created in Storyteq CMP, it is linked to a LUMA instance via a service account token. This token authorises CMP to communicate with LUMA and verify user identities when users log in.

Services control what authenticated users can do. Certain CMP features require specific LUMA services to be enabled for a user. For example, the Shares feature requires the Canopy > Shares service to be enabled on a per-user basis in LUMA.

Portal access is controlled by LUMA user groups. By default, if no groups are assigned to a portal, all users authenticated via the workspace’s LUMA instance can access it. Once one or more groups are assigned to a portal, access is restricted to members of those groups only.

Lenses are filters defined in LUMA that control which assets or templates are visible in a given context within CMP. Each lens is assigned to a domain, so the assets it returns are scoped to that domain’s content.

Domains are organisational units in LUMA that group assets, templates, and other content.