Enterprise operating model
Tenancy, entitlements, identity, billing and separation of duties for operating M2 Visibility as a corporate capability.
How to interpret this document
This content describes technical and methodological behavior that is implemented or explicitly planned in the product. When a control depends on configuration, a provider, a secret, a contract or legal approval, that dependency must remain visible.
Tenant
Organization is the primary tenant boundary. Workspace and Department add operational scope for business units and teams.
Entitlements
ENT-1.0 resolves plan and subscription, allows or blocks features, applies limits, calculates usage and records relevant decisions.
Identity
EID-1.0 adds verified domains, SSO policy, provider status, JIT provisioning, group mapping and SCIM lifecycle controls on top of Base44 authentication.
Billing
BILL-1.0 supports configured, custom and unconfigured price states, separates commercial billing from tax documents and reconciles the usage ledger against canonical measurement usage.
External dependencies
Controls such as mandatory SSO, SCIM, webhook signing and audit HMAC remain dependent on external providers or runtime secrets. The platform should not claim they are active when those dependencies are missing.