How Concepts Connect
This page shows how all the major concepts in MIDDAG Account relate to each other. If you have read the individual concept pages, this is the map that ties them together.
The relationship diagram
The chain, step by step
Everything in MIDDAG Account flows through two anchors: the Organization (your customer) and the Entitlement (what they have access to).
1. Organization is the customer
An Organization is a company or institution. It is the top-level container. Inside it:
- Collaborators are the people who belong to the organization. Each has a role (owner, admin, member, guest) and scopes that control what they can see.
- Orders, Invoices, and Quotes are the financial records tied to the organization.
- Entitlements are what the organization has access to.
2. Orders create entitlements
When a customer purchases a product (through a Quote that converts to an order, or through a direct purchase), the Order triggers the creation of one or more Entitlements.
The entitlement code (like PLG-2026050001) becomes the single reference for that customer relationship.
3. Entitlement class determines what is provisioned
The Entitlement Class (PLG, ENV, SVC, ORD, AFL, EDU) tells the system what kind of access the entitlement represents and what downstream resources to create:
| Class | Creates |
|---|---|
| PLG | License + Download |
| ENV | Environment + Service Request access |
| SVC | Service + Contract + Credit Balance + Service Requests |
| ORD | Order link + Invoice link + Download |
| AFL | Affiliate record |
| EDU | Order link + Document + Download |
4. Downstream resources live under the entitlement
Once created, the entitlement is the hub for everything related to that product or service:
- License -- software activation keys and authorized sites
- Contract -- service agreement with terms, SLA, and dates
- Service -- the type of work being delivered (hosting, support, consulting, etc.)
- Environment -- a managed hosting installation with health monitoring
- Credit Balance -- consumable credits for service-based work
- Service Request -- support tickets and change requests tracked against the entitlement
- Document -- shared files, certificates, and reports
- Invoice -- financial records linked through the order
When the entitlement's status changes (suspended, expired, cancelled), downstream resources follow. Suspend the entitlement and the license goes inactive, the environment pauses, and new service requests are blocked.
5. Policies govern the rules
Policies are configurable rules that control how entitlements behave at every stage: renewal, payment recovery, cancellation, SLA, credits, provisioning, trials, refunds, tier changes, and notifications.
Policies apply through a 5-level hierarchy:
Global > Entitlement Class > Organization > Product > Individual EntitlementThe most specific level wins. This means you can set sensible defaults globally and override them for specific customers, products, or even individual entitlements.
6. Entitlements can be sovereign
While the typical flow is Organization purchases Order which creates Entitlement, the entitlement does not require an Organization. It is a sovereign entity -- it can exist standalone for B2C customers, gift cards, promotional access, or migration imports where no organization mapping exists yet.
The full picture
Here is the complete flow from customer to access:
Read it this way: An Organization has Collaborators who can access the system. The Organization receives Quotes that convert to Orders. Orders create Entitlements. Each Entitlement has a Class that determines what downstream resources are provisioned. Policies govern the rules at every level. Invoices record the financial side.
One Organization, many entitlements
A single Organization typically has multiple entitlements -- one for each product or service they have purchased. Each entitlement has its own lifecycle, its own downstream resources, and its own policy overrides. The Organization is the umbrella; entitlements are the individual relationships underneath.
Example: Acme Corp might have:
PLG-2026030012-- a plugin license (active, renews in December)ENV-2026040003-- a managed Moodle environment (active)SVC-2026010001-- an ongoing support contract (active, 45 credits remaining)ORD-2025120088-- a one-time purchase (expired)
All four show up under Acme Corp's Organization page. Each has its own status, its own linked resources, and its own history. One admin view, four complete pictures.