SU · Subscriptions

Studio subscriptions · agency/enterprise plans · recurring access This page lists everything the Leumas graph records about how it relates to the rest of the system.

What SU · Subscriptions is

Studio subscriptions · agency/enterprise plans · recurring access It is recorded in the Leumas graph as a revenue in the architecture grain.

What SU · Subscriptions relates to

The graph records 2 relationships for it, across 2 kinds. It contains SU · Studio subscriptions.

What it depends on, and what depends on it

Nothing is recorded as a dependency of SU · Subscriptions. Nothing is recorded as depending on it, which for a leaf is normal and for a shared unit is worth checking.

Why it is shaped this way

Admin-led subscriptions cover Studio memberships, seats, agency plans, support plans, hosting tiers, and recurring access. Studio consumes the entitlement; Admin owns the offer, billing, renewal, and exception path.

How to read this

Every relationship here is one of nine shared kinds, mapped from the source graph rather than invented. A kind that a source uses and this model does not express is dropped and counted rather than turned into "related to", so what you see understates the source rather than embellishing it.

• Contains: SU · Studio subscriptions.
• Part of: Accounts.

Questions

What does SU · Subscriptions depend on?

This graph records no dependencies for SU · Subscriptions.

What uses SU · Subscriptions?

Nothing in this graph is recorded as depending on SU · Subscriptions.