Leumas Admin

Review · licenses · releases · trust This page lists everything the Leumas graph records about how it relates to the rest of the system.

What Leumas Admin is

Review · licenses · releases · trust It is recorded in the Leumas graph as a core in the architecture grain.

What Leumas Admin relates to

The graph records 18 relationships for it, across 3 kinds. It contains Accounts, Fleet and Marketplace, and 7 more.

What it depends on, and what depends on it

Leumas Admin depends on Leumas API, UI & theme, App Store, Revenue control plane and LeumasNode, and 2 more. 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

Leumas Admin owns the control side of revenue: memberships, pricing, marketplace review, first-party publishing, safety, licenses, contracts, payouts, risk, and releases.

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.

Questions

What does Leumas Admin depend on?

Leumas API, UI & theme, App Store, Revenue control plane, LeumasNode and App shell & nav, and 1 more.

What uses Leumas Admin?

Nothing in this graph is recorded as depending on Leumas Admin.