Governance, architecture and activation briefs
Trust and architecture centre
The reference product's seven governance and architecture briefs: each opens with the questions it answers, says what the platform owns and what a connected partner owns, and ends by showing what is live in TemasCRM.
- LiveWorks in this product; the link opens the screen.
- PartialPart of it exists; the note says what is missing.
- PlannedNot yet; on the roadmap.
- Not applicableNot done by this product's design; the note says why.
Governance
AI Model Hosting Governance
AI capabilities run on a routed, multi-provider architecture behind a single internal gateway, Minerva. This brief covers where Minerva and its providers are hosted, how customer configuration and data are scoped on shared serving infrastructure, and how AI or automated decision-making involvement can be surfaced on request.
2 Live3 Not applicable
Governance
Consent, Global Suppression and CEM Classification
A single, platform-wide mechanism lets customers opt out of all commercial communications in one action, and a template-level classification governs which messages carry consent and unsubscribe obligations and which do not. Both are native, live capabilities backed by an auditable change log.
5 Live1 Planned1 Not applicable
Governance
Offer Lifecycle Governance
An offer is managed as a single configuration object carrying its lifecycle state, eligibility rules, priority and consumption caps together. Toggling the state controls whether the offer is eligible to be shown; the same configuration enforces spend, redemption and stock limits in real time as each customer is evaluated, with role-based control over who can create or change it.
1 Live2 Partial3 Planned
Architecture
Multi-Brand Multi-Tenant Architecture
Each brand in a group operates with its own isolated data and governance while sharing common underlying infrastructure. Group-level reporting is aggregated across brand workspaces, and cross-brand controls such as shared caps are achieved through a group-level unification layer that sits atop the isolated workspaces, not by merging their data.
3 Live1 Planned1 Not applicable
Architecture
Pre-Built Connector Directory
The platform connects to loyalty, identity, retargeting, retail media, commerce, digital wallet and voice-of-customer platforms. Some are natively supported, pre-built connectors; others are integrated via the general-purpose API or the Partner Integration Framework. This brief sets out which is which, so integration effort can be scoped accurately.
2 Live3 Planned
Activation
Coupon Code Lifecycle
The platform generates, assigns and delivers unique coupon codes across every messaging channel, including tappable codes in WhatsApp, preserving uniqueness at the point of assignment. Redemption and purchase events are ingested back to drive follow-up targeting and measurement, while redemption status and fraud controls run in the connected coupon or POS platform.
4 Planned1 Not applicable
Activation
Retail Media Activation Suite
The platform provides the audience, personalization and measurement layer a retail media program runs on: prioritizing which offer a customer sees, suppressing out-of-stock products, placing sponsored content in owned channels, feeding paid media platforms with governed audiences, and measuring incrementality and new-to-brand impact. Delivery mechanics for paid, in-store and specialist formats are handled by connected partners.
1 Partial4 Planned2 Not applicable
Continue inside the product
Most of the controls these pages describe can be seen in the product: the consent ledger, the isolation report, approvals, the diagnostics board. Sign in, or start with the guides in the success centre.