Concepts

Platform, account and tenant; capability, solution, role and permission — the ideas the product is built on.

inlorus's screens are built on a few ideas, and without knowing them the screens can look odd: the same menu shows five groups to one person and one group to another; the same button works in one tenant and is refused in the next; a value can be written in one tenant and not in another. This section explains why.

The concepts are: the three scopes (platform, account, tenant) and how they connect; the path a capability takes from draft to being installed in a tenant; the five role archetypes and permission keys in the form <resource>.<verb>; how policy and configuration flow down from the scope above to the one below and why floors cannot be relaxed; the parts of the console that work the same way on every screen, and the four states a screen can show you.

These articles don't walk you through a task step by step; they explain why a task works the way it does. Come back here when you can't make sense of a refusal message or a screen that looks empty; the answer to most situations lies in the sentence “authority comes from an assignment, not from a key”.

Articles in Concepts