Holding / multi-entity explicit scope, no silent widening
Group exporters contract at holding level. Each sealed dossier still names one operator, one installation, and one reporting year — so verifiers never see a blurred boundary.
Can a holding company cover multiple operators in CBAMValid?
01Direct answer
Enterprise entitlement can sit at holding level while each sealed working file still binds one operator, one installation, and one reporting year. Cross-entity clones do not inherit payment unless the SOW says so.
The pressure you are under
Groups fear either paying per plant forever or blurring legal scope.
02Calculation
Holding structure does not merge emissions across entities in one seal.
03Explanation
Roles include Holding Admin, Operator Preparer, Internal Reviewer, Read-Only Verifier.
04Methodology
Explicit scope remains a seal invariant.
05Evidence
Published /enterprise/holding contract rules.
06Expert
No silent scope widening — verifiers see clear boundaries.
Each answer is written so a person — or an answer engine — can cite a single clear statement with supporting evidence and legal/product boundaries. Browse the full answer bank · Entity glossary
Direct answer
Can a holding company cover multiple operators and installations?
Enterprise entitlement can sit at holding level while each sealed working file still binds one operator, one installation, and one reporting year. Cross-entity clones do not inherit payment unless the SOW says so. Roles include Holding Admin, Operator Preparer, Internal Reviewer, and Read-Only Verifier.
Why this matters
Groups fear either paying forever per plant or blurring legal scope so verifiers reject the package.
Evidence
Holding scope page. Parent/child rules and seal-unit discipline Learn moreverified
Pricing tiers. Enterprise vs Single Pack scope contrast Learn moreverified
Direct answer
What does CBAMValid Enterprise Exclusive include?
Enterprise Exclusive starts from USD 12,000 per year (contact sales). It includes contracted SSO/IdP federation (Entra, Google, Okta), SLA draft and signed MSA path, holding/multi-entity entitlement, signed DPA path, API/onboarding, and verifier coordination. Not an accredited verification opinion. Single Pack remains self-serve at USD 449.
Why this matters
Multi-site buyers need procurement-grade SSO and SLA — not another self-serve checkbox.
Does CBAMValid Enterprise support SSO with Entra, Google, or Okta?
Yes under Enterprise contract. CBAMValid federates Microsoft Entra ID, Google Workspace, or Okta via OIDC or SAML. After IdP login, the server still issues an HttpOnly session cookie and enforces tenant/case authorization. SSO is not included on self-serve Single Pack.
Why this matters
IT security blocks SaaS tools that cannot join the corporate IdP. Checkbox “SSO coming soon” fails procurement.
Yes. CBAMValid publishes an Enterprise SLA draft with response targets for critical, high, and normal issues, plus an honest uptime posture based on Google Cloud / Firebase europe-west1. Binding credits live only in a signed Enterprise MSA. ISO 27001 and SOC 2 are not claimed.
Why this matters
Procurement packs need downloadable SLA language before legal review — not a vague “we take uptime seriously” sentence.
Evidence
SLA draft PDF. Public procurement starting point Learn moreverified
Security facts. Hosting region and subprocessors without fake certifications Learn moreverified
Direct answer
When should I buy Single Pack instead of Enterprise Exclusive?
Choose Single Pack (USD 449 pay-at-lock) for one working file — one operator, one installation, one reporting year — with same-file corrections included. Choose Enterprise Exclusive (from USD 12,000/year, contact sales) when you need SSO, SLA/DPA path, holding/multi-entity entitlement, API/onboarding, or coordinated multi-site rollout.
Why this matters
Buying Enterprise for a single plant wastes budget; buying Single Pack for a group IdP requirement fails IT review.
Evidence
Public pricing. Four tiers with Enterprise as the only contact-sales tier Learn moreverified
Sample dossier. Inspect the self-serve package before you pay Learn moreverified
Direct answer
Which Enterprise platform capabilities can buyers inspect?
Buyers can inspect published rulesets, the buyer share-link integrity flow, security and procurement documents, and the platform architecture before a scoping call. Additional regulatory categories beyond CBAM remain Enterprise statement-of-work only.
Why this matters
Enterprise buyers reject vaporware roadmaps. Modules must be inspectable before a scoping call.
Evidence
Published rulesets. Version-pinned CBAM ruleset registry Learn moreverified